Apparatuses, methods, and computer program products for centralized access permissions management of a plurality of application instances

ABSTRACT

Various embodiments of the present disclosure provide for centralized access permission management of a plurality of application instances. An example embodiment is configured to receive a manage access permissions request, cause rendering of a centralized access user interface, receive a domain access configuration request associated with a first domain, retrieve instance data associated with a plurality of application instances, cause rendering of a domain access configuration user interface associated with the first domain, receive a first product role selection request, generate a first domain permissions profile, the first domain permissions profile comprising at least a first product role associated with the first application instance, the first product role defining the role-based domain access permission of the first domain for accessing the first application instance, and store the first domain permissions profile in a permissions repository in association with the first domain and the first application instance.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.17/347,930 filed Jun. 15, 2021, which is incorporated by referenceherein in its entirety.

BACKGROUND

Various apparatuses, methods, and systems provide tools for managementof user access settings to various resources in application managementsystems. Applicant has identified a number of deficiencies and problemsassociated with effectively and efficiently configuring and centrallymanaging user access for a plurality of users to a plurality ofresources in existing application management systems. Through appliedeffort, ingenuity, and innovation, many of these identified deficienciesand problems have been solved by developing solutions that arestructured in accordance with the embodiments of the present disclosure,many examples of which are described in detail herein.

BRIEF SUMMARY

In general, embodiments of the present disclosure provided hereininclude improved apparatuses, methods, systems, and computer programproducts configured for managing access permissions for a plurality ofapplication instances in an application management system associatedwith an organization. In accordance with one exemplary embodiment of thepresent disclosure, an apparatus is provided for managing accesspermissions for a plurality of application instances associated with anorganization, the apparatus comprising at least one processor and atleast one non-transitory memory including program code, the at least onenon-transitory memory and the program code configured to, with the atleast one processor, cause the apparatus to receive a manage accesspermissions request from a computing device associated with an adminuser, the manage access permissions request comprising an organizationidentifier; cause rendering of a centralized access user interface to avisual display of the computing device associated with the admin user inresponse to receiving the manage access permissions request, thecentralized access user interface configured for managing accesspermissions of one or more domains; receive a domain accessconfiguration request associated with a first domain in response to userinteraction with the centralized access user interface; retrieveinstance data associated with a plurality of application instances, eachapplication instance associated with the organization identifier; causerendering, based on at least the instance data, of a domain accessconfiguration user interface associated with the first domain, thedomain access configuration user interface comprising a plurality ofapplication instance components, wherein each application instancecomponent represents a respective application instance of the pluralityof application instances and comprises a product role selectioninterface element; receive a first product role selection request inresponse to user interaction with a product role selection interfaceelement corresponding to a first application instance; generate a firstdomain permissions profile, wherein the first domain permissions profilecomprises at least a first product role associated with the firstapplication instance, the first product role defining the role-baseddomain access permission of the first domain for accessing the firstapplication instance; and store the first domain permissions profile ina permissions repository in association with the first domain and thefirst application instance.

In some embodiments, the first domain is a domain that has not beenpreviously permissioned such that the domain access configurationrequest comprises a create domain request requesting creation of thefirst domain and configuration of the access permissions of the firstdomain.

In other embodiments, the first domain is a previously-permissioneddomain such that domain access configuration request comprises a modifydomain request requesting modification of the access permissions of thefirst domain. In some embodiments, retrieving instance data associatedwith the plurality of application instances comprises querying thepermissions repository for domain permissions profiles associated withthe first domain. In further embodiments, causing rendering of thedomain access configuration user interface associated with the firstdomain comprises populating each product role selection interfaceelement with a product role corresponding to the respective applicationinstance based on the domain permissions profiles returned by the query.

In some embodiments, the apparatus is configured to receive a secondproduct role selection request in response to user interaction with aproduct role selection interface element associated with a secondapplication instance, update the first domain permissions profile suchthat the first domain permissions profile comprises at least the firstproduct role associated with the first application instance and a secondproduct role associated with the second application instance, the firstproduct role and second product role defining the role-based domainaccess permissions of the first domain for accessing the firstapplication instance and second application instance, respectively, andstore the updated first domain permissions profile in the permissionsrepository in association with the first domain, the first applicationinstance, and the second application instance.

In some embodiments, the apparatus is configured to receive a domainaccess configuration request associated with a second domain in responseto user interaction with the centralized access user interface, causerendering, based on the instance data, of a domain access configurationuser interface associated with the second domain, receive a secondproduct role selection request in response to user interaction with aproduct role selection interface element associated with the firstapplication instance, generate a second domain permissions profile,wherein the second domain permissions profile comprises a second productrole associated with the first application instance, the second productrole defining the role-based domain access permission of the seconddomain for accessing the first application instance; and store thesecond domain permissions profile in the permissions repository inassociation with the second domain and the first application instance.

In certain embodiments, the first domain is a domain associated with theorganization identifier. In other embodiments, the first domain is adomain not associated with the organization identifier.

In some embodiments, the domain access configuration user interfacefurther comprises an admin approval user interface element associatedwith each application instance component of the plurality of applicationinstance components, the admin approval user interface elementconfigured for receiving an admin approval parameter request.

In some embodiments, the instance data associated with an applicationinstance comprises one or more of an application instance identifier, anapplication instance name, an application instance URL, an applicationinstance permissions profile, a set of available product roles.

In some embodiments, the product role selection interface element forthe first application instance is associated with a plurality ofavailable product roles. In some further embodiments, the product roleselection interface element for the first application instance comprisesa drop down menu, the drop down menu listing the plurality of availableproduct roles associated with the first application instance, theproduct role selection interface element configured to receive a productrole selection.

In another example embodiment, an apparatus for programmaticallymanaging access permissions for a plurality of application instancesassociated with an organization is configured to receive an accessapplication instance request associated with an application instance,the application instance associated with an organization and the accessapplication instance request comprising a user email address identifierassociated with a user; parse the user email address identifier for anemail domain; query a permissions repository for a domain permissionsprofile based on the parsed email domain; in an instance wherein adomain permissions profile is returned by the query, determine whetherthe returned domain permissions profile comprises a product roleassociated with the requested application instance; and in an instancewherein the domain permissions profile comprises a product roleassociated with the requested application instance, provide the userwith access to the application instance based on a role-based domainaccess permission corresponding to the product role. In certain furtherembodiments, in response to determining that the domain permissionsprofile does not comprise a product role associated with the requestedapplication instance, the at least one non-transitory memory and theprogram code are further configured to, with the at least one processor,cause the apparatus to cause rendering of a request product access userinterface to a visual display of a computing device associated with theaccess application instance request; receive a request product accessrequest associated with the requested application instance in responseto user interaction with the request product access user interface;generate a request product access notification associated with therequested application instance, the request product access notificationcomprising the user email address identifier; and transmit the requestproduct access notification to at least one admin user associated withthe organization.

In another example embodiment, a method for managing access permissionsfor a plurality of application instances associated with an organizationcomprises receiving a manage access permissions request from a computingdevice associated with an admin user, the manage access permissionsrequest comprising an organization identifier; causing rendering of acentralized access user interface to a visual display of the computingdevice associated with the admin user in response to receiving themanage access permissions request, the centralized access user interfaceconfigured for managing access permissions of one or more domains;receiving a domain access configuration request associated with a firstdomain in response to user interaction with the centralized access userinterface; retrieving instance data associated with a plurality ofapplication instances, each application instance associated with theorganization identifier; causing rendering, based on at least theinstance data, of a domain access configuration user interfaceassociated with the first domain, the domain access configuration userinterface comprising a plurality of application instance components,wherein each application instance component represents a respectiveapplication instance of the plurality of application instances andcomprises a product role selection interface element; receiving a firstproduct role selection request in response to user interaction with aproduct role selection interface element corresponding to a firstapplication instance; generating a first domain permissions profile,wherein the first domain permissions profile comprises at least a firstproduct role associated with the first application instance, the firstproduct role defining the role-based domain access permission of thefirst domain for accessing the first application instance; and storingthe first domain permissions profile in a permissions repository inassociation with the first domain and the first application instance. Insome embodiments, the first domain is a domain that has not beenpreviously permissioned such that the domain access configurationrequest comprises a create domain request requesting creation of thefirst domain and configuration of the access permissions of the firstdomain. In other embodiments, the first domain is apreviously-permissioned domain such that domain access configurationrequest comprises a modify domain request requesting modification of theaccess permissions of the first domain.

In some embodiments, retrieving instance data associated with theplurality of application instances comprises querying the permissionsrepository for domain permissions profiles associated with the firstdomain. In some embodiments, causing rendering of the domain accessconfiguration user interface associated with the first domain comprisespopulating each product role selection interface element with a productrole corresponding to the respective application instance based on thedomain permissions profiles returned by the query.

In some embodiments, the method comprises receiving a second productrole selection request in response to user interaction with a productrole selection interface element associated with a second applicationinstance; updating the first domain permissions profile such that thefirst permissions profile comprises at least the first product roleassociated with the first application instance and a second product roleassociated with the second application instance, the first product roleand second product role defining the role-based domain accesspermissions of the first domain for accessing the first applicationinstance and second application instance, respectively; and storing theupdated first domain permissions profile in the permissions repositoryin association with the first domain, the first application instance,and the second application instance. In some embodiments, the methodfurther comprises receiving a domain access configuration requestassociated with a second domain in response to user interaction with thecentralized access user interface; causing rendering, based on theinstance data, of a domain access configuration user interfaceassociated with the second domain; receiving a second product roleselection request in response to user interaction with a product roleselection interface element associated with the first applicationinstance; generating a second domain permissions profile, wherein thesecond domain permissions profile comprises a second product roleassociated with the first application instance, the second product roledefining the role-based domain access permission of the second domainfor accessing the first application instance; and storing the seconddomain permissions profile in the permissions repository in associationwith the second domain and the first application instance.

In some embodiments, the first domain is a domain associated with theorganization identifier. In other embodiments, the first domain is adomain not associated with the organization identifier.

In some further embodiments, the domain access configuration userinterface further comprises an admin approval user interface elementassociated with each application instance component of the plurality ofapplication instance components, the admin approval user interfaceelement configured for receiving an admin approval parameter request.

In some embodiments, the instance data associated with an applicationinstance comprises one or more of an application instance identifier, anapplication instance name, an application instance URL, a domainpermissions profile, and a set of available product roles.In someembodiments, the product role selection interface element for the firstapplication instance is associated with a plurality of available productroles.

In some embodiments, the product role selection interface element forthe first application instance comprises a drop down menu, the drop downmenu listing the plurality of available product roles associated withthe first application instance, the product role selection interfaceelement configured to receive a product role selection.

In another example embodiment, a method for programmatically managingaccess permissions for a plurality of application instances associatedwith an organization, the method comprising receiving an accessapplication instance request associated with an application instance,the application instance associated with an organization and the accessapplication instance request comprising a user email address identifierassociated with a user; parsing the user email address identifier for anemail domain; querying a permissions repository for a domain permissionsprofile stored in association with the parsed email domain; in aninstance wherein a domain permissions profile is returned by the query,determine whether the returned domain permissions profile comprises aproduct role associated with the requested application instance; and inan instance wherein the domain permissions profile comprises a productrole associated with the requested application instance, provide theuser with access to the application instance based on a role-baseddomain access permission corresponding to the product role. In someembodiments, the domain permissions profile comprises an admin approvalparameter indicating that admin approval is required to access therequested application instance, prior to providing the user with accessto the requested application instance, the method further comprisescausing rendering of a request product access user interface to a visualdisplay of a computing device associated with the access applicationinstance request; receiving a request product access request associatedwith the requested application instance in response to user interactionwith the request product access user interface; generating a requestproduct access notification associated with the requested applicationinstance, the request product access notification comprising the useremail address identifier; and transmitting the request product accessnotification to at least one admin user associated with theorganization.

The above summary is provided merely for purposes of summarizing someexample embodiments to provide a basic understanding of some aspects ofthe present disclosure. Accordingly, it will be appreciated that theabove-described embodiments are merely examples and should not beconstrued to narrow the scope or spirit of the present disclosure in anyway. It will be appreciated that the scope of the present disclosureencompasses many potential embodiments in addition to those heresummarized, some of which will be further described below. Otherfeatures, aspects, and advantages of the subject matter will becomeapparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Having thus described certain example embodiments of the presentdisclosure in general terms above, non-limiting and non-exhaustiveembodiments of the subject disclosure will now be described withreference to the accompanying drawings which are not necessarily drawnto scale. The components illustrated in the accompanying drawings may ormay not be present in certain embodiments described herein. Someembodiments may include fewer (or more) components than those shown inthe drawings:

FIG. 1 illustrates an example application management system configuredto communicate with one or more admin devices and one or more userdevices in accordance with some example embodiments described herein;

FIG. 2 is a schematic block diagram of example circuitry for use in aproduct access configuration server in accordance with some exampleembodiments described herein;

FIG. 3 is a schematic block diagram of example circuitry for use in anadmin device or a user device for use by an admin user and user,respectively, in accordance with some example embodiments describedherein;

FIG. 4 illustrates an example centralized access user interface formanaging access permissions of one or more domains structured inaccordance with some example embodiments described herein;

FIG. 5A illustrates an example domain access configuration userinterface for adding a new domain, structured in accordance with someexample embodiments described herein;

FIG. 5B illustrates an example domain access configuration userinterface depicting an example interaction with a product role selectioninterface element for selecting a product role, structured in accordancewith some example embodiments described herein;

FIG. 5C illustrates an example updated domain access configuration userinterface depicting a selected product role, structured in accordancewith some example embodiments described herein;

FIG. 5D illustrates an example domain access configuration userinterface for editing a previously-permissioned domain, structured inaccordance with some example embodiments described herein;

FIG. 5E illustrates an example domain access configuration userinterface depicting an example interaction with a product role selectioninterface element for revising a product role, structured in accordancewith some example embodiments described herein;

FIG. 5F illustrates an example updated domain access configuration userinterface depicting a revised product role, structured in accordancewith some example embodiments described herein;

FIG. 6A illustrates an example product access user interface, structuredin accordance with some example embodiments described herein;

FIG. 6B illustrates an example request product access user interface,structured in accordance with some example embodiments described herein;

FIG. 7A is a flowchart illustrating example operations for managingaccess permissions for a plurality of application instances inaccordance with various aspects and embodiments of the subjectdisclosure;

FIG. 7B is a signal diagram of an example data flow in accordance withvarious aspects and embodiments of the subject disclosure;

FIG. 8 is a flowchart illustrating example operations for managingaccess permissions for a plurality of application instances inaccordance with various aspects and embodiments of the subjectdisclosure;

FIG. 9 is a flowchart illustrating example operations for managingaccess permissions for a plurality of application instances inaccordance with various aspects and embodiments of the subjectdisclosure;

FIG. 10A is a flowchart illustrating example operations forprogrammatically managing access permissions for a plurality ofapplication instances in accordance with various aspects and embodimentsof the subject disclosure;

FIG. 10B is a signal diagram of an example data flow in accordance withvarious aspects and embodiments of the subject disclosure;

FIG. 11 is a flowchart illustrating example operations forprogrammatically managing access permissions for a plurality ofapplication instances in response to an access application instancerequest associated with an unauthorized domain in accordance withvarious aspects and embodiments of the subject disclosure; and

FIG. 12 illustrates an example access requests user interface structuredin accordance with various embodiments of the present disclosure

DETAILED DESCRIPTION

One or more embodiments now will be more fully described with referenceto the accompanying drawings, wherein like reference numerals are usedto refer to like elements throughout. In the following description, forpurposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the various embodiments. Itis evident, however, that the various embodiments can be practicedwithout these specific details (and without applying to any particularnetworked environment or standard). It should be understood that some,but not all embodiments are shown and described herein. Indeed, theembodiments may be embodied in many different forms, and accordinglythis disclosure should not be construed as limited to the embodimentsset forth herein. Rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. As used herein,the description may refer to a server or user device as an example“apparatus.” However, elements of the apparatus described herein may beequally applicable to the claimed system, method, and computer programproduct. Accordingly, use of any such terms should not be taken to limitthe spirit and scope of embodiments of the present disclosure.

OVERVIEW

Apparatuses, methods, systems, and computer program products areprovided in accordance with example embodiments of the presentdisclosure in order to address technical problems associated withconfiguring and/or managing access permissions for a plurality ofapplication instances in an application management system. Anapplication management system enables an administrative user (e.g.,admin user) of an organization to configure and/or manage user accesssettings in order to permission or provision various users for accessinga plurality of resources, such as applications and application instancesassociated with the organization. As the management of such user accesssettings begins to grow in complexity, for example, over time as anincreasing number of applications and application instances are madeavailable and an increasing number of users from a variety of differentdomains require various levels of access to such resources, the task ofefficiently managing the access permissions also increases incomplexity. Individual management of each user, or even at theindividual application instance level, can become impractical. It isundesirable to require an admin user to separately access the useraccess settings associated with each individual application instance ina multi-instance environment as such inefficiency needlessly increasescomputational load and traffic. Further, such a process for accesspermissions management increases user frustration for admin users.Accordingly, the inventors have determined it would be desirable andadvantageous to have centralized access permissions management withvariable domain permissioning in an application management system.Embodiments herein provide apparatuses, systems, computer-implementedmethods, and computer program products for centralized accesspermissions management of a plurality of application instances in anapplication management system. Some such embodiments provide improvedfunctionality for managing any number of access permissions, forexample, to manage access permissions for a plurality of applicationinstances across multiple platforms in a centralized access userinterface, thereby allowing for reduced operations compared to managingaccess permissions for such application instances individually.

The inventors have also determined it would be desirable andadvantageous to be able to provision users with varied accesspermissions to a plurality of application instances without having tomanually permission each individual user. By way of non-limitingexample, consider Jennifer, an admin user for Acme Corporation, needingto permission access for XYZ Corporation to an Acme HR instance ofConfluence® for purposes of an audit. It would be efficient for Jenniferto be able to broadly permission users associated with the “xyz.com”domain to the Confluence® application via domain access permissions,however, in a multi-instance environment, it is undesirable to broadlygive the same users access to the entire Confluence® application (i.e.,all instances of Confluence®). For example, it would be undesirable toalso allow users of “xyz.com” domain to have access to Acme's internalknowledge instance of Confluence® simply because “xyz.com” is anauthenticated domain permissioned to access the Acme HR instance ofConfluence®. In this regard, such unfettered access to the entireConfluence® application may potentially pose data security and/or dataprivacy vulnerabilities. To efficiently permission a variety of userswith respect to multiple instances of any number of applications withoutrequiring admin Jennifer to separately and individually access theadministrative settings for each application instance and to improve theuser experience associated with assigning such access permissions (e.g.,reduce the computational load/traffic required as well as interactionsrequired by Jennifer), various embodiments of the present disclosure,utilizing user interactions with a centralized access user interface andan associated domain access configuration user interface, facilitatemanaging access permissions for a selected domain (e.g., xyz.com) withrespect to a plurality of application instances. Some embodimentsfacilitate such variable domain permissioning by associating suchselected domain with a selected product role for each respectiveapplication instance, the selected product role defining the role-baseddomain access permissions for such domain with respect to eachcorresponding application instance. For example, with respect to Acme'sHR instance of Confluence® and Acme's internal knowledge instance ofConfluence®, using various embodiments of the present disclosure, adminJennifer can associate “xyz.com” with an “auditing” product role withrespect to the HR instance of Confluence® and with a “None” or “Noproduct access” product role with respect to Acme's internal knowledgeinstance of Confluence®, thereby preventing access by XYZ users toAcme's internal knowledge instance of Confluence®.

By way of another non-limiting example, using various embodiments of thepresent disclosure, admin Jennifer can permission users associated withthe domain of Alpha Customer (“alpha.com”) to have a “Customer” productrole with respect to an instance of Jira® associated with softwaredevelopment for Alpha Customer and she can permission users associatedwith the domain of Beta Customer (“beta.com”) to have a “Customer”product role with respect to an instance of Jira® associated withsoftware development for Beta Customer. Jennifer can further permissiona “None” or “No product access” product role or not assign any productrole (e.g., providing no access) to users associated with the domain ofBeta Customer with respect to the instance of Jira® associated withsoftware development for Alpha Customer, thereby preventing users ofBeta Customer from accessing Alpha Customer's data. Similarly, Jennifercan further permission a “None” or “No product access” product role ornot assign any product role (e.g., providing no access) to usersassociated with the domain of Alpha Customer with respect to theinstance of Jira® associated with software development for BetaCustomer, thereby preventing users of Alpha Customer from accessing BetaCustomer's data.

In accordance with various embodiments of the present disclosure, adminusers can assign varied access permissions to a single applicationinstance in a domain-centered way. In this regard, in anothernon-limiting example, admin Jennifer can permission users associatedwith the Acme domain (“acme.com”) to have a “Developer” product role ina customer service instance of Jira® while also permissioning usersassociated with the domain of Alpha Customer (“alpha.com”) to have aseparate “Helpseeker” product role with respect to the same customerservice instance of Jira®. In some embodiments, the level or type ofaccess provided to the selected application instance is defined by theproduct role, the parameters, settings, entitlements, and indications ofrights of which can be separately determined, defined, or assigned.

Accordingly, example embodiments of the present disclosure includeenabling an admin user to permission users associated with a firstdomain in accordance with a product role defining a role-based domainaccess permission for accessing a first application instance.Additionally or alternatively, further embodiments enable an admin userto permission such first domain with a product role defining arole-based domain access permission for accessing a second applicationinstance, wherein, in certain embodiments, the product role associatedwith the second application instance differs from the product roleassociated with the first application instance. Additionally oralternatively still, certain embodiments enable an admin user topermission users associated with a second domain with a product roledefining a role-based domain access permission for accessing the samefirst application instance, wherein, in certain embodiments, the productrole associated with the second domain differs from the product roleassociated with the first domain for accessing the first applicationinstance. Some such embodiments provide functionality for configuringone or more associated improved user interfaces enabling centralizedaccess permissions management of any number of application instances toreduce the number of user interactions required for managing accesspermissions for such application instances.

Example embodiments of the present disclosure address the variousdeficiencies set forth above and otherwise described herein, while alsoproviding various technical benefits. For example, some embodiments ofthe present disclosure increase the efficiency and effectiveness of anapplication management system itself. For example, the amount of systemresources expended and time allocated to determining individual useraccess permissions is costly and is only exacerbated as the number ofapplication instances and users increase. Accordingly, some embodimentsof the present disclosure reduce such computing resource consumption bythe product access configuration server by generating a domainpermissions profile and enabling role-based domain access permissions atthe organization level (e.g., as opposed to the individual applicationinstance level). Such reduced data processing amounts to less strain onthe application management system itself, leading to increased lifetimeand efficiency of the system. In addition, the role-based domain accesspermissions enable data security and data privacy across multipleinstances of an application. As such, systems structured in accordancewith various embodiments of the present disclosure may reduce computingresource consumption and provide specific, technical solutions totechnical problems faced by existing systems, the details of which aredescribed hereafter.

DEFINITIONS

As used herein, the terms “data,” “content,” “digital content,” “digitalcontent object,” “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present invention.Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present invention. Further, where acomputing device is described herein to receive data from anothercomputing device, it will be appreciated that the data may be receiveddirectly from another computing device or may be received indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like, sometimes referred to herein as a “network.”Similarly, where a computing device is described herein to send data toanother computing device, it will be appreciated that the data may betransmitted directly to another computing device or may be transmittedindirectly via one or more intermediary computing devices, such as, forexample, one or more servers, relays, routers, network access points,base stations, hosts, and/or the like.

The term “user device” refers to computer hardware and/or software thatis configured to access a service made available by a server, such as aproduct access configuration server of an application management system.The server is often (but not always) on another computer system, inwhich case the user device accesses the service by way of a network.User devices include, without limitation, smart phones, tabletcomputers, laptop computers, wearables, personal computers, enterprisecomputers, and the like. In some embodiments, a user device isassociated with a user. The association may be created by the userdevice transmitting authentication information associated with the userto the application management system.

The term “application management system” refers to a software platformand associated hardware that is configured to support, maintain, andmanage administration settings associated with one or more applicationsand/or application instances of an organization.

As used herein, the term “user identifier” refers to one or more itemsof data by which a user may be identified within an applicationmanagement system. For example, a user identifier may comprise textstring(s), numerical character(s), alphabetical character(s),alphanumeric code(s), ASCII character(s), a pointer, an IP address, aMAC address, a memory address, other unique identifier, or a combinationthereof.

An organization may include one or more “administrative users” or “adminusers”, which refer to a user associated with the organization who hasthe administrative authority to manage the computing devices (e.g., userdevices, servers, etc.) and associated resources of the organization.For example, an admin user has the authority to make decisions, onbehalf of other users (e.g., non-administrative or non-admin users),with respect to the computing devices and/or associated resources of theorganization. In some embodiments, an admin user has the authority todefine one or more access permissions for a resource of theorganization. In some embodiments, an admin user is associated with an“admin user identifier”, which refers to an identifier that indicatesthe user is an admin user of an organization. A client computing deviceassociated with an admin user is referred to as an “admin device”.

The term “organization” refers to one or more data structures by which aset of users are associated with a particular entity (e.g., employees orcontractors of different companies may be of separate organizations).The term “organization identifier” refers to one or more items of databy which an organization may be uniquely identifier. A non-limitingexample of an organization identifier comprises American Standard Codefor Information Interchange (ASCII) text, a pointer, a memory address, aunique numerical and/or string value, and the like.

The terms “application,” “software application,” “app,” “product,” orsimilar terms refer to a computer program or group of computer programsdesigned to perform coordinated functions, tasks, or activities for thebenefit of a user or group of users. In certain embodiments, anapplication is designed for use by and interaction with one or morelocal, networked or remote computing devices, such as, but not limitedto, user devices and/or admin devices. Examples of applications mayinclude, but is not limited to, a project management and issue trackingapplication (e.g., Jira® by Atlassian), a knowledge management andcollaboration application (e.g., Confluence® by Atlassian), workflowengines, scheduling engines, service desk incident management system,cloud services, word processors, spreadsheet generators, accountingapplications, web browsers, messaging applications, email clients, mediaplayers, file viewers, videogames, photo/video editors, and/or the like.In some embodiments, an application is a cloud product.

The terms “application instance” and “instance” refer to a single ordistinct occurrence of a software application running on a server orgroup of servers (e.g., a physical or virtual servers in a cloud-basedcomputing environment). An organization may have one or more applicationinstances or instances of each software application associated with suchorganization. For example, an organization may operate a selected singleapplication as a single instance or as multiple instances (e.g., amulti-instance environment). An application instance can be madeaccessible to one or more users. In some embodiments, an applicationinstance is hosted by or associated with a particular site (e.g., URL).For example, in a first non-limiting exemplary illustration, AcmeCorporation has a single instance of Jira® and a single instance ofConfluence®, each associated with a single site (e.g.,all.acme.atlassian.com). In a second non-limiting exemplaryillustration, XYZ Corporation has first instances of Jira® andConfluence® associated with its finance team atsite.finance.xyz.atlassian.com and second instances of each of Jira® andConfluence® associated with its development team atsite.dev.xyz.atlassian.com. In such example, although the underlyinginstallation, functionality, and capabilities of various applicationinstances may be the same, the data, data sets, information, messages,users, etc. associated with and populating a particular instance of anapplication can differ from other instances. For instance, in theprevious example of XYZ Corporation, the users, data, information, etc.associated with the finance instance of Jira® can (and likely will)differ from the users, data, information, etc. associated with thedevelopment instance of Jira®. An organization may have multipleinstances of an application for a variety of reasons, including, but notlimited to, providing or preserving autonomy of existing, new, and/oracquired teams and departments of the organization (e.g., uniquecustomization), data isolation (e.g., keep sensitive data separate) forsecurity purposes, based on geography (e.g., sites, projects, and/orteams), and/or the like. In some embodiments, an application instance isassociated with an “application instance identifier”, which refers toone or more items of data by which a particular application instance ofan organization may be identified within an application managementsystem.

The term “instance data” refers to any data related to an applicationinstance, such as, but not limited to, application instance identifier,application instance name, domain permissions profile, applicationinstance URL (e.g., site hosting the application instance), availableproduct roles (e.g., a set of available product roles), defined productroles, and any other data that may serve to distinguish one or moreinstances from each other. In some embodiments, instance data includesapplication instance plan identifier, such application instance planidentifier associated with a selection of features that areassociated/available with respect to the selected application instanceplan. For example, whether the selected application instance plan isfree, standard, premium, or enterprise defines which features areassociated with the selected application instance plan in an applicationmanagement system.

The term “domain data” refers to any data related to a domain, such as,but not limited to, domain identifier (e.g., email domain identifier),domain name, domain permissions profile, domain licensee count, definedproduct roles, date the domain was added, date the domain was lastedited, enablement/disablement data, and any other data that may serveto distinguish one or more domains from each other.

As used herein, the term “access permissions” refers to one or moreparameters, configurations, provisions, settings, levels, entitlements,indications of rights and/or permissions data associated with accessingone or more requested resources that indicate to an access configurationserver certain users or types of users that are permissioned orauthorized to access the one or more requested resources orfunctionality, and in some instances, defining the level or type ofaccess available to such users. For example, in some embodiments, a useror group of users is associated with a particular level or type ofaccess to a given resource, whereby the user or group of users aregranted access to certain features of the given resource but not others.In some embodiments, an access permission is associated with a domainidentifier, indicating that a user with an email address with the samedomain identified by domain identifier is permissioned to access therequested resource. Such access permissions are “domain accesspermissions.” For example, a domain access permission may authorize allusers with email addresses that end in “acme.com” access to therequested resource. This would broadly give access to a selectedresource to any user who is a member of Acme Corporation and has acorresponding email address. This type of access permission is usefulwhen an admin user desires to make an application available to everyonewithin an organization or group. Additionally or alternatively, in someembodiments, such as multi-instance environments for example, productroles are associated with a domain such that the level or type of accessprovided to users from such domain can be separately specified ordefined for each application instance. Such access permissions are“role-based domain access permissions.”

The term “product access configuration server” refers to a softwareplatform and associated hardware that is configured to manage access tothe various resources of an organization, such as applications orindividual application instances. The product access configurationserver is accessible via one or more computing devices, is configured toreceive configuration and/or permissions requests, and access one ormore data repositories, such as a permissions repository and/or anapplications repository. The functionality of the product accessconfiguration server may be provided via a single server or a collectionof servers having a common functionality, or the functionality of theproduct access configuration server may be segmented among a pluralityof servers or collections of servers performing subsets of the describedfunctionality of the product access configuration server, such as in acloud server environment.

The term “manage access permissions request” refers to an electricallygenerated digital object created by a computing device that indicatesthat a user (e.g., an admin user) has provided an input comprising arequest to configure and/or manage access permissions for one or moreresources of an organization. A manage access permissions request may berepresented via a temporary code that notifies a recipient (e.g., aproduct access configuration server) that a user has made the request.To provide further context, a manage access permissions request isgenerated in response to a user interaction with a computing devicewherein a user causes the computing device to generate a manage accesspermissions request by interacting with, for example, a specific accesspermissions configuration actuator button or interface element renderedon a visual display of the computing device (e.g., an admin userclicking on “User Access Settings”). In some embodiments, the manageaccess permissions request is associated with at least an organizationidentifier (e.g., such that the request is associated with a particularorganization) and/or other data for use in retrieving organizationrelevant data for rendering a centralized access user interface asdescribed herein. For example, in a non-limiting exemplary illustration,Jennifer is an admin user for Acme Corporation and in response toJennifer selecting the “User Access Settings” interface elementassociated with an administration user interface for Acme Corporation inthe application management system, a manage access permissions request,comprising an organization identifier associated with Acme Corporation,is generated at Jennifer's admin device and transmitted via a network toa server (e.g., product access configuration server). In someembodiments, an admin user identifier associated with Jennifer isassociated with the manage access permissions request.

The term “centralized access user interface” refers to a user interfacethat is rendered to a visual display and is specially configured toenable a user (e.g., an admin user) to centrally configure and/or manageaccess permissions for one or more resources of an organization. In someembodiments, a centralized access user interface is configured to enablean admin user to identify, select, and/or create one or more domains(e.g., an email domain) in order to further define access permissions ofusers associated with such one or more domains. Exemplary centralizedaccess user interfaces may be rendered in any desired form including,but not limited to, as a mobile application for display on a mobilecomputing device (e.g., a smartphone, table computer, etc.), a webpageor website for display on a mobile or non-mobile computing device viathe Internet, and the like. For example, the centralized access userinterface 400 of FIG. 4 is an example of a centralized access userinterface.

The term “domain access configuration request” refers to an electricallygenerated digital object created by a computing device that indicatesthat a user (e.g., an admin user) has provided an input comprising arequest to configure and/or manage access permissions for usersassociated with a selected domain such that the selected domain ispermissioned. A domain access configuration request may be representedvia a temporary code that notifies a recipient (e.g., a product accessconfiguration server) that a user has made the request. To providefurther context, a domain access configuration request is generated inresponse to a user interaction with a computing device wherein a usercauses the computing device to generate a domain access configurationrequest by interacting with, for example, a specific domain accesspermissions configuration actuator button or interface element renderedon a visual display of the computing device. For example, in someembodiments, the selected domain is a new domain to be created, such aswhen an admin user clicks on an “Add Domain” interface element in acentralized access user interface as depicted in FIG. 4 tocreate/configure access permissions for a selected new domain. In someembodiments, the domain is an existing domain (e.g.,previously-permissioned domain), such as when an admin user clicks on an“Edit” interface element associated with representation of the existingdomain, as depicted in FIG. 4 , to edit/manage access permissions forthe selected existing domain.

In some embodiments, the selected domain is associated with a domainidentifier, such that the request comprises a domain identifierassociated with the selected domain. A “domain identifier” refers to oneor more items of data by which a particular domain may be identified.For example, in a non-limiting exemplary illustration, Jennifer is anadmin user for Acme Corporation and in response to Jennifer selectingthe “Edit” interface element associated with existing domain “acme.com”in a centralized access user interface for Acme Corporation, a domainaccess configuration request, comprising a domain identifier associatedwith “acme.com”, is generated at Jennifer's admin device and transmittedvia a network to a server (e.g., product access configuration server).In some embodiments, a nonspecific domain identifier is associated witha domain (e.g., new domain to be created) until a unique domainidentifier is associated with the domain.

The term “domain access configuration user interface” refers to a userinterface that is rendered to a visual display and is configured toenable a user (e.g., an admin user) to configure and/or manage accesspermissions of a plurality of application instances with respect to aselected domain. Exemplary domain access configuration user interfacesmay be rendered in any desired form including, but not limited to, as amobile application for display on a mobile computing device (e.g., asmartphone, table computer, etc.), a webpage or website for display on amobile or non-mobile computing device via the Internet, and the like.For example, the domain access configuration user interfaces 500 ofFIGS. 5A-5F are examples of domain access configuration user interfaces.

In some embodiments, a domain access configuration user interfacecomprises a domain name interface component. The term “domain nameinterface component” refers to a user interface element that is renderedas a portion of a domain access configuration user interface and isconfigured to enable a user to create and/or modify a domain name (e.g.,text string) for the selected domain. For example, the domain nameinterface component 510 of FIGS. 5A-5F are examples of domain nameinterface components.

In some embodiments, a domain access configuration user interfacecomprises one or more application instance components. The term“application instance component” refers to a listing, identification, orany other representation of an application instance in a domain accessconfiguration user interface. For example, in some embodiments, eachapplication instance component is based on instance data of eachrespective application instance of a plurality of application instancesassociated with an organization. In some embodiments, an applicationinstance component is associated with an application instance identifierand comprises a corresponding instance name associated with theapplication instance identifier. In some embodiments, an applicationinstance component comprises a product role selection interface element.Additionally or alternatively, in some embodiments, an applicationinstance component comprises an admin approval user interface element.

The term “product role selection interface element” refers to a userinterface element that is rendered as a portion of a domain accessconfiguration user interface and is configured to enable a user (e.g.,admin user) to define (e.g. select) a product role to be assigned to theselected domain with respect to accessing the associated applicationinstance. For example, the product role selection interface elements 520of FIGS. 5A-5F are examples of product role selection interfaceelements. In some embodiments, the product role selection interfaceelement is populated with one or more available product role(s)associated with the selected application instance.

The term “product role” refers to a defined set of one or moreparameters, configurations, provisions, settings, levels, entitlements,indications of rights and/or permissions data associated with accessingone or more requested resources, particularly defining the level or typeof access available to user or group of users. In some embodiments, aproduct role can be used to broadly define the role-based domain accesspermissions of a set of users associated with a selected domain. Productroles include, but are not limited to, user, guest, helpseeker,developer, customer, auditor, product administrator (“Product Admin”),view only, reporting, none (e.g., a product role defining no productaccess), any other product role that may serve to define access to aresource. For example, in some embodiments, a product admin product roleis permissioned to alter settings for a particular product (e.g.,workflows, settings, and schemas). In some embodiments, a view onlyproduct role is permissioned to view content in the selected applicationinstance, but is restricted from other access. In other embodiments, aview only product role is permissioned to view content and comment inthe selected application instance, but is restricted from other access.In some embodiments, a reporting product role is permissioned to accessand alter certain content, such as dashboards, reports, and roadmaps.Such a reporting product role enables a user to report progress, forexample, to executives/management. In some embodiments, a guest productrole is permissioned to view and edit pages on selected sites to whichthe user is granted access, however, is restricted from viewing otheruses outside the space. In certain embodiments, a helpseeker productrole is permissioned to raise customer support tickets. In someembodiments, a customer product role is permissioned to raise customersupport tickets as well as have access as otherwise specificallyconfigured by an admin user.

In some embodiments, available product roles are pre-defined. In somefurther embodiments, available product roles are associated with and/ordefined by an application instance plan identifier (e.g., free,standard, premium, enterprise, etc.). In still further embodiments, oneor more product roles are configurable and/or defined by eachorganization (e.g., via admin user) in a separate user interface andassociated with the product role selection interface element(s).

The term “product role selection request” refers to an electricallygenerated digital object created by a computing device upon userengagement with a product role selection interface element thatindicates that a user has provided a selection of an available productrole to be associated with a selected domain for a particularapplication instance. A product role selection request may berepresented via a temporary code that is generated at an admin device(e.g., a client device of an admin user) and is transmitted to arecipient (e.g., a server) to notify the recipient that an admin userhas made the request. To provide further context, a product roleselection request is generated in response to a user interaction with acomputing device, for example, with a domain access configuration userinterface associated with a selected domain. In some embodiments, a usercauses the computing device to generate a product role selection requestby interacting with a product role selection interface element toindicate a selection of an available product role, for example, from adropdown menu or via a radio button associated with an available productrole rendered on a visual display of the computing device. For instance,in a non-limiting example, Jennifer, an admin user of Acme Corporationwho desires to provide users of domain xyz.com with auditingcapabilities (e.g., auditing access permission) with respect to an AcmeHR instance of Confluence® indicates such desire by clicking on a radiobutton associated with the “Auditor” product role from a set ofavailable product roles associated with the HR instance of Confluence®,the set of available product roles rendered as part of a product roleselection interface element for the HR instance of Confluence® in adomain access configuration user interface associated with xyz.com. In afurther non-limiting example, admin Jennifer of Acme Corporation alsodesires to provide users of domain xyz.com with customer accesscapabilities (e.g., customer access permission) with respect to anexternal facing customer instance of Confluence®. To do so, adminJennifer clicks on a radio button associated with the “Customer” productrole from a set of available product roles associated with the externalfacing customer instance of Confluence®, the set of available productroles rendered as part of a product role selection interface element forthe external facing customer instance of Confluence® in a domain accessconfiguration user interface associated with xyz.com. In still a furthernon-limiting example, admin Jennifer of Acme Corporation also desires toprevent users of domain xyz.com from accessing an Acme internalknowledge instance of Confluence®. To do so, admin Jennifer clicks on aradio button associated with the “None” product role from a set ofavailable product roles associated with the internal knowledge instanceof Confluence®, the set of available product roles rendered as part of aproduct role selection interface element for the internal knowledgeinstance of Confluence® in a domain access configuration user interfaceassociated with xyz.com.

The term “admin approval user interface element” refers to a userinterface element that is rendered as a portion of a domain accessconfiguration user interface and is configured to receive an adminapproval parameter request, thereby enabling a user (e.g., admin user)to define an admin approval access parameter associated with thecorresponding application instance. For example, the admin approval userinterface element 530 of FIGS. 5C, 5D, 5E, and 5F are examples of adminapproval user interface elements.

The term “admin approval access parameter” refers to a parameterindicating whether approval by an admin user is required before a useris granted access to a selected resource (e.g., an applicationinstance).

The term “domain permissions profile” refers to a domain-specific datastructure or aggregation of a plurality of application instances andcorresponding product role(s) associated with each application instance,each product role defining the role-based domain access permission ofthe associated domain for accessing the selected application instance.In some embodiments, a domain permissions profile is generated at theapplication management system (e.g., product access configurationserver) in response to receipt of a product role selection requestcomprising a selected product role to be associated with thecorresponding application instance in a domain access configuration userinterface. In some embodiments, the domain permissions profile is storedin a database, for example, a permissions database, in association withat least the associated domain. In further embodiments, the domainpermissions profile is stored in association with correspondingapplication instances for the selected domain.

The term “access application instance request” refers to an electricallygenerated digital object created by a computing device that indicatesthat a user has provided an input comprising a request to access aselected application instance. An access application instance requestmay be represented via a temporary code that notifies a recipient (e.g.,a product access configuration server) that a user has made the request.

The term “request product access user interface” refers to a userinterface that is rendered to a visual display and is configured toenable a user to interact with the interface to generate a requestproduct access request that is transmitted to, for example, the productaccess configuration server. The term “request product access request”refers to an electrically generated digital object created by acomputing device that indicates that a user has provided an inputcomprising a request for admin approval to access a selected applicationinstance. Exemplary request product access user interfaces may berendered in any desired form including, but not limited to, as a mobileapplication for display on a mobile computing device (e.g., asmartphone, table computer, etc.), a webpage or website for display on amobile or non-mobile computing device via the Internet, and the like.For example, the request product access user interface 650 of FIG. 6B isan example of a request product access user interface.

The term “permissions repository” refers to a location, such as databasestored on a memory device, which is accessible by one or more computingdevices for retrieval and storage of data associated with accesspermissions. For example, the permissions repository includes one ormore of domain permissions profile(s), instance identifier(s), domainidentifier(s), product role(s), access permission(s) (e.g., role-basedaccess permission(s)), and/or the like. The permissions repository maybe a dedicated device and/or a part of a larger repository. Thepermissions repository may be dynamically updated or be static. In someembodiments, the permissions repository is encrypted in order to limitunauthorized access of such permissions data.

The term “applications repository” refers to a location, such asdatabase stored on a memory device, which is accessible by one or morecomputing devices for retrieval and storage of data associated withapplications and application instances. For example, the applicationsrepository includes one or more of application instance identifier(s),domain identifier(s), product role(s) (e.g., available product role(s)),domain permissions profile(s), and/or the like. The applicationsrepository may be a dedicated device and/or a part of a largerrepository. The applications repository may be dynamically updated or bestatic. In some embodiments, the applications repository is encrypted inorder to limit unauthorized access of such data.

The term “comprising” means including but not limited to and should beinterpreted in the manner it is typically used in the patent context.Use of broader terms such as comprises, includes, and having should beunderstood to provide support for narrower terms such as consisting of,consisting essentially of, and comprised substantially of

The phrases “in one embodiment,” “according to one embodiment,” and thelike generally mean that the particular feature, structure, orcharacteristic following the phrase may be included in the at least oneembodiment of the present invention and may be included in more than oneembodiment of the present invention (importantly, such phrases do notnecessarily refer to the same embodiment).

The terms “illustrative,” “example,” “exemplary” and the like are usedherein to mean “serving as an example, instance, or illustration” withno indication of quality level. Any implementation described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other implementations.

The terms “about,” “approximately,” or the like, when used with anumber, may mean that specific number, or alternatively, a range inproximity to the specific number, as understood by persons of skill inthe art field.

If the specification states a component or feature “may,” “can,”“could,” “should,” “would,” “preferably,” “possibly,” “typically,”“optionally,” “for example,” “often,” or “might” (or other suchlanguage) be included or have a characteristic, that particularcomponent or feature is not required to be included or to have thecharacteristic. Such component or feature may be optionally included insome embodiments, or it may be excluded.

The term “set” refers to a collection of one or more items.

The term “plurality” refers to two or more items.

The term “or” is used herein in both the alternative and conjunctivesense, unless otherwise indicated.

EXAMPLE SYSTEM ARCHITECTURE

Methods, apparatuses, systems, and computer program products of thepresent disclosure may be embodied by any of a variety of computingdevices. For example, the method, apparatus, system, and computerprogram product of an example embodiment may be embodied by a networkeddevice (e.g., an enterprise platform), such as a server or other networkentity, configured to communicate with one or more devices, such as oneor more user devices or one or more admin devices. Additionally, oralternatively, the computing device may include fixed computing devices,such as a personal computer or a computer workstation. Still further,example embodiments may be embodied by any of a variety of mobiledevices, such as a portable digital assistant (PDA), mobile telephone,smartphone, laptop computer, tablet computer, wearable, or anycombination of the aforementioned devices.

With reference to FIG. 1 , an example computing system 100 within whichsome embodiments of the present disclosure operate is illustrated. Inparticular, FIG. 1 illustrates an example application management system200 configured to communicate with one or more admin devices 103A-103Nand one or more user devices 101A-101N in accordance with some exampleembodiments described herein. Users and admin users may access anapplication management system 200 via a communications network 102 usingone or more of user devices 101A-101N and admin devices 103A-103N,respectively. Application management system 200 may comprise a productaccess configuration server 210 in communication with at least onerepository, such as permissions repository 215 and/or applicationsrepository 220. Such repository(ies) may be hosted by the product accessconfiguration server 210 or otherwise hosted by devices in communicationwith the product access configuration server 210. The applicationmanagement system 200 is, in some embodiments, able to facilitate accessand central management of access permissions to a plurality ofapplication(s) and application instance(s), as will be described below.

Product access configuration server 210 may include circuitry, networkedprocessors, or the like configured to perform some or all of the productaccess configuration server-based processes described herein, and may beany suitable network server and/or other type of processing device. Insome embodiments, product access configuration server 210 may generate adomain permissions profile and/or transmit commands and instructions forrendering a centralized access user interface and domain accessconfiguration server user interfaces to admin devices 103A-103N, usingdata from, for example, permissions repository 215 and/or applicationsrepository 220. In this regard, the product access configuration server210 may be embodied by any of a variety of devices, for example, theproduct access configuration server 210 may be embodied as a computer ora plurality of computers. For example, product access configurationserver 210 may be configured to receive/transmit data and may includeany of a variety of fixed terminals, such as a server, desktop, orkiosk, or it may comprise any of a variety of mobile terminals, such asa portable digital assistant (PDA), mobile telephone, smartphone, laptopcomputer, tablet computer, or in some embodiments, a peripheral devicethat connects to one or more fixed or mobile terminals. Exampleembodiments contemplated herein may have various form factors anddesigns but will nevertheless include at least the componentsillustrated in FIG. 2 and described in connection therewith. In someembodiments, product access configuration server 210 may be locatedremotely from the permissions repository 215 and/or applicationsrepository 220, although in other embodiments, the product accessconfiguration server 210 may comprise the permissions repository 215and/or applications repository 220. The product access configurationserver 210 may, in some embodiments, comprise several servers orcomputing devices performing interconnected and/or distributedfunctions. Despite the many arrangements contemplated herein, productaccess configuration server 210 is shown and described herein as asingle computing device to avoid unnecessarily overcomplicating thedisclosure.

Product access configuration server 210 can communicate with one or moreuser devices 101A-101N and/or one or more admin devices 103A-103N viacommunications network 102. Communications network 102 may include anyone or more wired and/or wireless communication networks including, forexample, a wired or wireless local area network (LAN), personal areanetwork (PAN), metropolitan area network (MAN), wide area network (WAN),or the like, as well as any hardware, software and/or firmware requiredfor implementing the one or more networks (e.g., network routers,switches, hubs, etc.). For example, communications network 102 mayinclude a cellular telephone, mobile broadband, long term evolution(LTE), GSM/EDGE, UMTS/HSPA, IEEE 802.11, IEEE 802.16, IEEE 802.20,Wi-Fi, dial-up, and/or WiMAX network. Furthermore, the communicationsnetwork 102 may include a public network, such as the Internet, aprivate network, such as an intranet, or combinations thereof, and mayutilize a variety of networking protocols now available or laterdeveloped including, but not limited to TCP/IP based networkingprotocols. For instance, the networking protocol may be customized tosuit the needs of the application management system 200.

Permissions repository 215 may be stored by any suitable storage deviceconfigured to store some or all of the information described herein(e.g., memory 201 of the product access configuration server 210 or aseparate memory system separate from the product access configurationserver 210, such as one or more database systems, backend data servers,network databases, cloud storage devices, or the like provided byanother device (e.g., online application or 3rd party provider), such asa Network Attached Storage (NAS) device or devices, or as a separatedatabase server or servers. Permissions repository 215 may comprise datareceived from the product access configuration server 210 (e.g., via amemory 201 and/or processor(s) 202), and the corresponding storagedevice may thus store this data. Permissions repository 215 includesinformation accessed and stored by the product access configurationserver 210 to facilitate the operations of the application managementsystem 200. As such, permissions repository 215 may include, forexample, without limitation, instance data, application instanceidentifier(s), domain data, domain identifier(s), organizationidentifier(s), admin user identifier(s), domain permissions profile(s),access permission(s) (e.g., role-based domain access permission(s)),product role(s) and/or the like.

Similarly, applications repository 220 may be stored by any suitablestorage device configured to store some or all of the informationdescribed herein (e.g., memory 201 of the product access configurationserver 210 or a separate memory system separate from the product accessconfiguration server 210, such as one or more database systems, backenddata servers, network databases, cloud storage devices, or the likeprovided by another device (e.g., online application or 3rd partyprovider), such as a Network Attached Storage (NAS) device or devices,or as a separate database server or servers. Applications repository 220may comprise data received from the product access configuration server210 (e.g., via a memory 201 and/or processor(s) 202), and thecorresponding storage device may thus store this data. Applicationsrepository 220 includes information accessed and stored by the productaccess configuration server 210 to facilitate the operations of theapplication management system 200. As such, applications repository 220may include, for example, without limitation, user identifier(s),application instance identifier(s), application instance name(s),application instance URL(s), domain permissions profile(s), productrole(s), instance data, and/or the like.

The user devices 101A-101N and admin devices 103A-103N may beimplemented as any computing device as defined above. Electronic datareceived by the product access configuration server 210 from the userdevices 101A-101N and admin devices 103A-103N may be provided in variousforms and via various methods. For example, the user devices 101A-101Nand admin devices 103A-103N may include desktop computers, laptopcomputers, smartphones, netbooks, tablet computers, wearables, and/orother networked device, that may be used for any suitable purpose inaddition to presenting the product access configuration user interfaceto a user (e.g., planning user) and otherwise providing access to theapplication management system 200. The depictions in FIG. 1 of “N” userdevices and “N” admin devices are merely for illustration purposes.According to some embodiments, the user devices 101A-101N may beconfigured to display an interface on a display of the user device forviewing, editing, and/or otherwise interacting with at least one productaccess user interface, which may be provided by the applicationmanagement system 200. According to further embodiments, the userdevices 101A-101N may be configured to display a request product accessuser interface and/or the like. According to still further embodiments,the admin devices 103A-103N may be configured to, among otheroperations, display an interface on a display of the admin device forviewing, editing, and/or otherwise interacting with one or more of acentralized access user interface, a domain access configuration userinterface, a product role selection interface element, and/or adminapproval user interface element.

In embodiments where a user device 101A-101N or an admin device103A-103N is a mobile device, such as a smartphone or tablet, the userdevice 101A-101N or admin device 103A-103N may execute an “app” tointeract with the application management system 200. Such apps aretypically designed to execute on mobile devices, such as tablets orsmartphones. For example, an app may be provided that executes on mobiledevice operating systems such as iOS®, Android®, or Windows®. Theseplatforms typically provide frameworks that allow apps to communicatewith one another and with particular hardware and software components ofmobile devices. The mobile operating systems named above each provideframeworks for interacting with, for example, wired and wireless networkinterfaces, user contacts, and other applications. Communication withhardware and software modules executing outside of the app is typicallyprovided via application programming interfaces (APIs) provided by themobile device operating system. Additionally, or alternatively, the userdevice 101A-101N or admin device 103A-103N may interact with theapplication management system 200 via a web browser. As yet anotherexample, the user devices 101A-101N and admin devices 103A-103N mayinclude various hardware or firmware designed to interface with theapplication management system 200.

Example Apparatus for Implementing Embodiments of the Present Disclosure

FIG. 2 shows a schematic block diagram of example circuitry, some or allof which may be included in a product access configuration server 210.In accordance with some example embodiments, product accessconfiguration server 210 may include various means, such as memory 201,processor 202, input/output circuitry 203, and/or communicationscircuitry 204. In some embodiments, permissions circuitry 205 may alsoor instead be included. For example, where permissions circuitry 205 isincluded in product access configuration server 210, permissionscircuitry 205 may be configured to facilitate the functionalitydiscussed herein regarding managing access permissions for a pluralityof applications instances, including but not limited to, generating,causing storage of, updating, and/or retrieving domain permissionsprofile(s). An apparatus, such as product access configuration server210, may be configured, using one or more of the circuitry 201, 202,203, 204, and 205, to execute the operations described above withrespect to FIG. 1 and below in connection with FIGS. 4-12 .

Although the use of the term “circuitry” as used herein with respect tocomponents 201-205 are described in some cases with respect tofunctional limitations, it should be understood that the particularimplementations necessarily include the use of particular hardwareconfigured to perform the functions associated with the respectivecircuitry as described herein. It should also be understood that certainof these components 201-205 may include similar or common hardware. Forexample, two sets of circuitry may both leverage use of the sameprocessor, network interface, storage medium, or the like to performtheir associated functions, such that duplicate hardware is not requiredfor each set of circuitry.

The term “circuitry” should also be understood, in some embodiments, toinclude software for configuring the hardware. For example, in someembodiments, “circuitry” may include processing circuitry, storagemedia, network interfaces, input/output devices, and the like. In someembodiments, other elements of the product access configuration server210 may provide or supplement the functionality of particular circuitry.For example, the processor 202 may provide processing functionality, thememory 201 may provide storage functionality, the communicationscircuitry 204 may provide network interface functionality, and the like.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 201 via a bus forpassing information among components of, for example, product accessconfiguration server 210. The memory 201 is non-transitory and mayinclude, for example, one or more volatile and/or non-volatile memories,or some combination thereof. In other words, for example, the memory 201may be an electronic storage device (e.g., a computer readable storagemedium). The memory 201 may be configured to store information, data,content, applications, instructions, or the like, for enabling anapparatus, e.g., product access configuration server 210, to carry outvarious functions in accordance with example embodiments of the presentdisclosure.

Although illustrated in FIG. 2 as a single memory, memory 201 maycomprise a plurality of memory components. The plurality of memorycomponents may be embodied on a single computing device or distributedacross a plurality of computing devices. In various embodiments, memory201 may comprise, for example, a hard disk, random access memory, cachememory, flash memory, a compact disc read only memory (CD-ROM), digitalversatile disc read only memory (DVD-ROM), an optical disc, circuitryconfigured to store information, or some combination thereof. Memory 201may be configured to store information, data, applications,instructions, or the like for enabling product access configurationserver 210 to carry out various functions in accordance with exampleembodiments discussed herein. For example, in at least some embodiments,memory 201 is configured to buffer data for processing by processor 202.Additionally or alternatively, in at least some embodiments, memory 201is configured to store program instructions for execution by processor202. Memory 201 may store information in the form of static and/ordynamic information. This stored information may be stored and/or usedby product access configuration server 210 during the course ofperforming its functionalities.

Processor 202 may be embodied in a number of different ways and may, forexample, include one or more processing devices configured to performindependently. Additionally or alternatively, processor 202 may includeone or more processors configured in tandem via a bus to enableindependent execution of instructions, pipelining, and/ormultithreading. Processor 202 may, for example, be embodied as variousmeans including one or more microprocessors with accompanying digitalsignal processor(s), one or more processor(s) without an accompanyingdigital signal processor, one or more coprocessors, one or moremulti-core processors, one or more controllers, processing circuitry,one or more computers, various other processing elements includingintegrated circuits such as, for example, an ASIC (application specificintegrated circuit) or FPGA (field programmable gate array), or somecombination thereof. The use of the term “processing circuitry” may beunderstood to include a single core processor, a multi-core processor,multiple processors internal to the apparatus, and/or remote or “cloud”processors. Accordingly, although illustrated in FIG. 2 as a singleprocessor, in some embodiments, processor 202 comprises a plurality ofprocessors. The plurality of processors may be embodied on a singlecomputing device or may be distributed across a plurality of suchdevices collectively configured to function as product accessconfiguration server 210. The plurality of processors may be inoperative communication with each other and may be collectivelyconfigured to perform one or more functionalities of product accessconfiguration server 210 as described herein.

In an example embodiment, processor 202 is configured to executeinstructions stored in the memory 201 or otherwise accessible toprocessor 202. Alternatively or additionally, the processor 202 may beconfigured to execute hard-coded functionality. As such, whetherconfigured by hardware or software methods, or by a combination thereof,the processor 202 may represent an entity (e.g., physically embodied incircuitry) capable of performing operations according to an embodimentof the present disclosure while configured accordingly. Alternatively,as another example, when the processor 202 is embodied as an executor ofsoftware instructions, the instructions may specifically configureprocessor 202 to perform one or more algorithms and/or operationsdescribed herein when the instructions are executed. For example, theseinstructions, when executed by processor 202, may cause product accessconfiguration server 210 to perform one or more of the functionalitiesof product access configuration server 210 as described herein.

In some embodiments, input/output circuitry 203 may, in turn, be incommunication with processor 202 to provide an audible, visual,mechanical, or other output and/or, in some embodiments, to receive anindication of an input. In that sense, input/output circuitry 203 mayinclude means for performing analog-to-digital and/or digital-to-analogdata conversions. Input/output circuitry 203 may include support, forexample, for a display, touchscreen, keyboard, button, click wheel,mouse, joystick, an image capturing device (e.g., a camera), motionsensor (e.g., accelerometer and/or gyroscope), microphone, audiorecorder, speaker, biometric scanner, and/or other input/outputmechanisms. Input/output circuitry 203 may comprise a user interface(e.g., a centralized access user interface, a domain accessconfiguration user interface, a product role selection interfaceelement, an admin approval user interface element, a product access userinterface, a request product access user interface, etc.) and maycomprise a web user interface, a mobile application, a kiosk, or thelike. The processor 202 and/or user interface circuitry comprising theprocessor 202 may be configured to control one or more functions of adisplay or one or more user interface elements through computer programinstructions (e.g., software and/or firmware) stored on a memoryaccessible to the processor 202 (e.g., memory 201, and/or the like). Insome embodiments, aspects of input/output circuitry 203 may be reducedas compared to embodiments where product access configuration server 210may be implemented as an end-user machine or other type of devicedesigned for complex user interactions. In some embodiments (like othercomponents discussed herein), input/output circuitry 203 may even beeliminated from product access configuration server 210. Input/outputcircuitry 203 may be in communication with memory 201, communicationscircuitry 204, and/or any other component(s), such as via a bus.Although more than one input/output circuitry and/or other component canbe included in product access configuration server 210, only one isshown in FIG. 2 to avoid overcomplicating the disclosure (e.g., like theother components discussed herein).

Communications circuitry 204, in some embodiments, includes any means,such as a device or circuitry embodied in either hardware, software,firmware or a combination of hardware, software, and/or firmware, thatis configured to receive and/or transmit data from/to a network and/orany other device, circuitry, or module in communication with productaccess configuration server 210. In this regard, communicationscircuitry 204 may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, in some embodiments, communications circuitry 204 is configuredto receive and/or transmit any data that may be stored by memory 201using any protocol that may be used for communications between computingdevices. For example, communications circuitry 204 may include one ormore network interface cards, antennae, transmitters, receivers, buses,switches, routers, modems, and supporting hardware and/or software,and/or firmware/software, or any other device suitable for enablingcommunications via a network. Additionally or alternatively, in someembodiments, communications circuitry 204 includes circuitry forinteracting with the antenna(s) to cause transmission of signals via theantenna(e) or to handle receipt of signals received via the antenna(e).These signals may be transmitted by product access configuration server210 using any of a number of wireless personal area network (PAN)technologies, such as Bluetooth® v1.0 through v3.0, Bluetooth Low Energy(BLE), infrared wireless (e.g., IrDA), ultra-wideband (UWB), inductionwireless transmission, or the like. In addition, it should be understoodthat these signals may be transmitted using Wi-Fi, Near FieldCommunications (NFC), Worldwide Interoperability for Microwave Access(WiMAX) or other proximity-based communications protocols.Communications circuitry 204 may additionally or alternatively be incommunication with the memory 201, input/output circuitry 203 and/or anyother component of product access configuration server 210, such as viaa bus.

In some embodiments, permissions circuitry 205 may also or instead beincluded and configured to perform the functionality discussed hereinrelated to managing access permissions of a plurality of applicationsinstances. In some embodiments, permissions circuitry 205 includeshardware, software, firmware, and/or a combination of such components,configured to support various aspects of such centralized accessmanagement-related functionality, features, and/or services of theproduct access configuration server 210 as described herein. It shouldbe appreciated that in some embodiments, permissions circuitry 205performs one or more of such exemplary actions in combination withanother set of circuitry of the product access configuration server 210,such as one or more of memory 201, processor 202, input/output circuitry203, and communications circuitry 204. For example, in some embodiments,permissions circuitry 205 utilizes processing circuitry, such as theprocessor 202 and/or the like, to perform one or more of itscorresponding operations. In a further example, in some embodiments,some or all of the functionality of permissions circuitry 205 may beperformed by processor 202. In this regard, some or all of the exampleprocesses and algorithms discussed herein can be performed by at leastone processor 202 and/or permissions circuitry 205. It should also beappreciated that, in some embodiments, permissions circuitry 205 mayinclude a separate processor, specially configured field programmablegate array (FPGA), or application specific interface circuit (ASIC) toperform its corresponding functions.

Additionally or alternatively, in some embodiments, permissionscircuitry 205 utilizes memory 201 to store collected information. Forexample, in some implementations, permissions circuitry 205 includeshardware, software, firmware, and/or a combination thereof, thatinteracts with permissions repository 215, applications repository 220,and/or memory 201 to send, retrieve, update, and/or store data valuesembodied by and/or associated with instance data, domain data,organization identifier(s), application instance identifier(s), domainidentifier(s), user identifier(s), admin user identifier(s), applicationinstance name(s), application instance URL(s), email addressidentifier(s), domain permissions profile(s), product role(s), accesspermission(s) (e.g., role-based domain access permission(s)) andassociated data that is configured for association with managing accesspermissions of a plurality of application instances including, forexample, generating a domain permissions profile, and to support theoperations of the permissions circuitry 205 and the remaining circuitry.Additionally or alternatively, in some embodiments, permissionscircuitry 205 utilizes input/output circuitry 203 to facilitate useroutput (e.g., causing rendering of one or more user interface(s) such asa centralized access user interface), and/or to receive user input(e.g., user clicks, user taps, keyboard interactions, user gesture,and/or the like). Additionally or alternatively still, in someembodiments, the permissions circuitry 205 utilizes communicationscircuitry 204 to initiate transmissions to another computing device,receive transmissions from another computing device, communicate signalsbetween the various sets of circuitry as depicted, and/or the like.

Accordingly, non-transitory computer readable storage media can beconfigured to store firmware, one or more application programs, and/orother software, which include instructions and other computer-readableprogram code portions that can be executed to control processors of thecomponents of product access configuration server 210 to implementvarious operations, including the examples shown herein. As such, aseries of computer-readable program code portions may be embodied in oneor more computer program products and can be used, with a device,product access configuration server 210, database, and/or otherprogrammable apparatus, to produce the machine-implemented processesdiscussed herein. It is also noted that all or some of the informationdiscussed herein can be based on data that is received, generated and/ormaintained by one or more components of the product access configurationserver 210. In some embodiments, one or more external systems (such as aremote cloud computing and/or data storage system) may also be leveragedto provide at least some of the functionality discussed herein.

Some embodiments of the present disclosure run outside of theapplication management system 200, such as, for example, on an apparatus300. In some embodiments, the apparatus 300 is embodied as depicted anddescribed in FIG. 3 . FIG. 3 is a schematic block diagram is illustratedshowing example circuitry, some or all of which may be included in anexample apparatus 300 (e.g., a user device 101A-101N or an admin device103A-103N), configured to enable a user to access the applicationmanagement system 200 in accordance with certain embodiments of thepresent disclosure. For example, in some embodiments, the apparatus 300embodies an admin device 103A-103N and is configured to enable an adminuser to access the application management system 200 to centrally manageaccess permissions of a plurality of application instances. In stillfurther embodiments, the apparatus 300 embodies a user device 101A-101Nand is configured to enable a user to interact with the applicationmanagement system 200 to be authenticated and/or obtain access to aselected application instance.

In accordance with some example embodiments, apparatus 300 may includevarious means, such as memory 301, processor 302, input/output circuitry303, and/or communications circuitry 304. Apparatus 300, such as a userdevice 101A-101N or an admin device 103A-103N, may be configured, usingone or more of the circuitry 301, 302, 303, and 304, to execute theoperations described above with respect to FIG. 1 and below inconnection with FIGS. 4-12 .

In some embodiments, apparatus 300 communicates with applicationmanagement system 200 (for example, embodied by the product accessconfiguration server 210 as depicted and described with respect to FIG.2 ). It should be appreciated that, in some embodiments, an applicationmanagement system 200 communicates with any number of apparatus(es) 300.It should be appreciated that the components 301-304 may be embodiedsimilar to that of the similarly named components described with respectto FIG. 2 . For purposes of brevity and length of disclosure, duplicatedescription of such functionality is omitted. Nevertheless, these deviceelements, operating together, provide the respective apparatuses withthe functionality necessary to facilitate the communication of data(e.g., manage access permissions request(s), domain access configurationrequest(s), instance data, domain data, organization identifier(s),application instance identifier(s), admin user identifier(s), productrole selection request(s), domain permissions profile(s), create domainrequest(s), modify domain request(s), and/or the like) for managingaccess permissions for a plurality of application instances. That is,the apparatus 300, in some embodiments, is configured, using one or moresets of circuitry 301, 302, 303, and/or 304, to execute the operationsdescribed herein.

As described above and as will be appreciated based on this disclosure,embodiments of the present disclosure may be configured as systems,methods, apparatuses, computing devices, personal computers, servers,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions embodied in the computer-readable storage medium(e.g., computer software stored on a hardware device). Any suitablecomputer-readable storage medium may be utilized includingnon-transitory hard disks, CD-ROMs, flash memory, optical storagedevices, or magnetic storage devices.

As will be appreciated, any such computer program instructions and/orother type of code may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor, or other programmable circuitry that execute thecode on the machine creates the means for implementing variousfunctions, including those described herein in connection with thecomponents of product access configuration server 210, user devices101A-101N, and admin devices 103A-103N.

The computing systems described herein can include clients and servers.A client and server are generally remote from each other and typicallyinteract through a communication network. The relationship of client andserver arises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits information/data (e.g., an HTML page) toa user device (e.g., for purposes of displaying information/data to andreceiving user input from a user interacting with a user device or anadmin user interacting with an admin device). Information/data generatedat the user device (e.g., as a result of the user interaction with anadmin device) can be received from the user device (e.g., user device oradmin device) at the server.

EXAMPLE USER INTERFACES FOR CENTRALIZED ACCESS PERMISSIONS MANAGEMENT

In various embodiments of the present disclosure, an apparatus (e.g.,product access configuration server 210) is configured to manage accesspermissions for a plurality of application instances associated with anorganization in an application management system 200. FIGS. 4, 5A, 5B,5C, 5D, 5E, 5F, 6A, 6F, and 12 illustrate example user interfaces andsub-interfaces including various information and enabling variousfunctionality for such centralized access permissions management, inaccordance with example embodiments of the present disclosure. It shouldbe appreciated that the information depicted in the various userinterfaces is exemplary, and that similar and/or alternative data,parameters, data values, and/or the like may be provided. Additionallyor alternatively, in some embodiments, the layout of the variousinterface elements, and/or sub-interfaces of each depicted userinterface may differ without deviating from scope of this disclosure.Further, it should be appreciated that, in some embodiments, data and/orinformation for centralized access permissions management may beprovided without one or more corresponding user interfaces, for example,via one or more APIs made available via an application management system200 (e.g., product access configuration server 210). As such, theexample depicted interfaces, sub-interfaces, elements, and data valuesdepicted therein are provided for descriptive and illustrative purposesand are not to limit the scope or spirit of the disclosure herein.

FIG. 4 illustrates an example centralized access user interface 400structured in accordance with various embodiments of the presentdisclosure. In some embodiments, the centralized access user interfaceis rendered to a client device, for example, an admin device 103A-103Nassociated with an admin user. In some embodiments, an applicationmanagement system 200 (e.g., product access configuration server 210)causes rendering of the centralized access user interface 400 inresponse to receiving a manage access permissions request from the admindevice 103A-103N to the application management system 200 (e.g., productaccess configuration server 210). For example, in response to userinteraction with an application management user interface associatedwith the application management system 200 (e.g., product accessconfiguration server 210), a manage access permissions request isgenerated at a client device (e.g., an admin device 103A-103N) andtransmitted to the application management system 200 (e.g., productaccess configuration server 210). In a non-limiting example, selectionof a settings configuration interface element, such as a “Join settings”or “User access settings” (not depicted), rendered in a sidebar portionof an application management user interface with respect to a “Products”category tab, a manage access permissions request is generated at theclient device. In some embodiments, the centralized access userinterface 400 is a default interface rendered to the visual display of aclient device (e.g., admin user) in response to selection of a“Products” category tab (not depicted) associated with managingapplications of the organization.

In certain embodiments, the manage access permissions request comprisesone or more data objects (e.g., unique identifier(s)) associated withthe requesting user to authenticate or otherwise identify the requestinguser as an admin user. For example, in some further embodiments, themanage access permissions request comprises an admin user identifierassociated with the requesting admin user. In some embodiments, an admindevice 103A-103N receives or accesses the admin user identifier. Forexample, in some embodiments, the admin user identifier is receivedremotely, via wireless communication or tethered communication, ordirectly, via input into one of the admin devices 103A-103N associatedwith the admin user. In some embodiments, the admin user has a remotedevice, such as a mobile device or key fob that interacts with the admindevice 103A-103N to transmit an admin user identifier and/or otherrelated user data to authenticate the admin user. In another example, anadmin user simply provides login credentials through the interface oftheir admin device 103A-103N. The admin device 103A-103N then transfersthe unique admin user identifier to the application management system200 (e.g., the product access configuration server 210) as part of or inaddition to the manage access permissions request.

In some embodiments, the manage access permissions request comprises anorganization identifier corresponding to the organization with which therequesting admin user is associated. In some embodiments, theapplication management system 200 (e.g., the product accessconfiguration server 210) uses the organization identifier (or otherunique identifier) to inform the population of data and information tobe included or rendered as part of the centralized access user interface400 and/or a domain access configuration user interface 500. Forexample, in certain embodiments, the application management system 200(e.g., the product access configuration server 210) retrieves domaindata (e.g., domain name(s), enablement/disablement status for thedomain(s), date each domain was added, date each domain was last edited,etc.) associated with one or more domains based on the organizationidentifier. In some embodiments, the application management system 200(e.g., the product access configuration server 210) retrieves instancedata (e.g., application instance identifier for each applicationinstance associated with domain, an application instance name such as acustom application instance name, an application instance URL, etc.)associated with a plurality of application instances based on theorganization identifier. In some embodiments, the application managementsystem 200 (e.g., the product access configuration server 210) retrievesone or more additional data items to be included or rendered as part ofthe centralized access user interface 400 and/or a domain accessconfiguration user interface 500, including but not limited to,application name for each application instance associated with thedomain and application logo for each application instance associatedwith the domain. Such examples of unique identifier(s), however, are forpurposes of illustration and not of limitation and other suitablevariations of authenticating and/or associating the manage accesspermissions request with an organization are also contemplated by thisdisclosure as will be apparent to one of ordinary skill in the art. Forexample, in some embodiments, the corresponding organization isdetermined and/or parsed from an admin user identifier.

As illustrated, the centralized access user interface 400 of FIG. 4 isconfigured for managing access permissions of one or more domains.Specifically, the centralized access user interface 400 presents domaindata associated with one or more domains, for example, a domain accessset 416. In some embodiments, the depicted one or more domains havepreviously been associated with the organization of the admin user. Insome embodiments, the application management system 200 (e.g., productaccess configuration server 210) queries a permissions database based onthe organization identifier to retrieve any domains associated with theorganization (e.g., domains that have been previously-permissioned withrespect to the organization). In other words, in some embodiments, atleast one of the domains of the domain access set 416 is a domain thathas been previously approved, authenticated, permissioned or otherwisemanaged with respect to at least one application instance or applicationassociated with the organization. For example, in the example embodimentdepicted in FIG. 4 , each of acme.com, acme.com.au, alpha.com, andbeta.com domains have previously been permissioned with respect to atleast one produce (e.g., application instance) associated with theorganization. In some embodiments, a generic or catch-all default domain(e.g., “Any domain” as depicted in the centralized access user interface400 of FIG. 4 ), for which access permissions can be centrally managed,is included in the centralized access user interface 400. For example,in an instance in which an organization does not have any specificdomain added or previously-permissioned, the domain access set 416depicted in the centralized access user interface 400 may only identifyor list the generic or catch-all default domain (e.g., admin user seesonly the “Any domain” item). In this regard, the centralized access userinterface 400 presents a domain access set 416, each row or line in thedomain access set 416 representing a domain for which access permissionsmay be managed by the admin user (e.g., management domains).

It should be appreciated that the centralized access user interface 400may be configured to include various parameters or data associated witha domain, and such parameters or data are not limited to the exemplaryparameters and data depicted in FIG. 4 . In an example context, asillustrated, a domain name column 402 includes a data value for aparameter representing an identification of each domain in the domainaccess set 416. For example, “acme.com” is presented in the second rowof the domain access set 416 in the exemplary centralized access userinterface 400 depicted in FIG. 4 . Additionally or alternatively, asillustrated, a product application column 404 includes a data value fora parameter representing the number of products or resources (e.g.,application instances) to which the corresponding domain is currentlymanaged. For example, “acme.com” currently is managed with respect to 3products (e.g., application instances) in the exemplary centralizedaccess user interface 400 depicted in FIG. 4 . Additionally oralternatively, as illustrated, a domain enablement column 406 includes adata value for a parameter representing whether or not the accesspermission(s) associated with the corresponding domain are enabled. Forexample, the access permissions associated with “acme.com” is currentlyenabled in the exemplary centralized access user interface 400 depictedin FIG. 4 . The domain enablement data value allows an admin user toquickly and easily enable or disable configured access permissions atthe domain level. In some instances, when a new domain is created andconfigured, the default domain enablement data value is disabled suchthat an admin user must affirmatively enable the configured accesspermissions. In some embodiments, each domain of the domain access set416 is depicted with a toggle button in the domain enablement column406. Such example of a toggle button, however, is for purposes ofillustration and not of limitation and other suitable variations ofselecting or de-selecting domain enablement are also contemplated bythis disclosure as will be apparent to one of ordinary skill in the art.For example, in some embodiments, a checkbox interface element or radiobutton is associated with each domain.

It should be appreciated that a centralized access user interface 400may be configured to include any of various types of information. Forexample, in at least some example embodiments, the centralized accessuser interface 400 is configured to include one or more of a domainrecency indicator indicating if a domain was recently added or createdwith respect to the organization (e.g., “NEW” as depicted with respectto “acme.com.au” in FIG. 4 ), a domain information interface element forpresenting additional information about the corresponding domain in asub-interface, and/or the like.

Additionally or alternatively, in some embodiments, user interactionwith the centralized access user interface 400 causes rendering ofanother interface, or sub-interface, for viewing, altering, creating,and/or otherwise managing the access permissions associated with aselected domain. For example, in some embodiments, a domain accessconfiguration user interface 500 as depicted in FIGS. 5A and 5D isgenerated in response user interaction with the centralized access userinterface 400. FIG. 5A illustrates an example domain accessconfiguration user interface 500 associated with creating a new domainthat has not been previously permissioned with respect to theorganization, the example domain access configuration user interface 500structured in accordance with various embodiments of the presentdisclosure. FIG. 5D illustrates an example domain access configurationuser interface 500 associated with modifying a domain that has beenpreviously permissioned with respect to the organization, the exampledomain access configuration user interface 500 structured in accordancewith various embodiments of the present disclosure. In some embodiments,the domain access configuration user interface 500 is rendered to aclient device, for example, an admin device 103A-103N associated withthe admin user, in response to user interaction with the centralizedaccess user interface 400 as described herein. For example, in someembodiments, an application management system 200 (e.g., product accessconfiguration server 210) causes rendering of the domain accessconfiguration user interface 500 in response to receiving a domainaccess configuration request from the admin device 103A-103N to theapplication management system 200 (e.g., product access configurationserver 210), the domain access configuration request associated with aselected domain. In some embodiments, the domain access configurationrequest is associated with a domain identifier of the selected domain asdescribed herein.

In some embodiments, the domain access configuration request comprisesone or more additional requests. For example, in certain embodiments,user interaction with a domain creation interface element generates adomain access configuration request at the client device (e.g., theadmin device 103A-103N associated with the admin user), the domainaccess configuration request further comprising a create domain requestrequesting creation of a new domain and configuration of the accesspermissions for the new domain. In such embodiments, the selected domainis a new domain that has not been previously permissioned with respectto any of the products or resources (e.g., plurality of applicationinstances) associated with the organization. For example, userinteraction with the “Add domain” domain creation interface element 410as depicted in FIG. 4 generates a domain access configuration request,the receipt of which at the application management system 200 (e.g.,product access configuration server 210) causes rendering of a domainaccess configuration user interface 500 or sub-interface, specificallyan add new domain access configuration user interface 500 as depicted inFIG. 5A, for managing (e.g., creating) access permissions for a newdomain.

Additionally or alternatively, a domain edit interface element 408 isassociated with each domain of the displayed domain access set 416 inthe centralized access user interface 400 as depicted in FIG. 4 . Inthis regard, in at least some embodiments, user interaction with adomain edit interface element 408 generates a domain accessconfiguration request at the client device (e.g., the admin device103A-103N associated with the admin user), the domain accessconfiguration request comprising a modify domain request requestingmodification of the access permissions previously permissioned for thecorresponding domain. For example, “acme.com” is apreviously-permissioned domain depicted in the centralized access userinterface 400 of FIG. 4 and selection of the “Edit” domain editinterface element associated with “acme.com” generates a domain accessconfiguration request, the receipt of which at the applicationmanagement system 200 (e.g., product access configuration server 210)causes rendering of a domain access configuration user interface 500 orsub-interface, specifically an edit domain access configuration userinterface 500 as depicted in FIG. 5D, based on the selected “acme.com”domain of the domain access set 416.

In certain embodiments, the domain access configuration requestcomprises one or more data objects, for example, a domain identifierassociated with the selected domain to identify the selected domain tothe application management system 200 (e.g., product accessconfiguration server 210). For instance, in some embodiments, when theselected domain is a previously-permissioned domain (e.g., the adminuser has selected the “Edit” interface element associated withpreviously-permissioned “acme.com” domain), the domain accessconfiguration request comprises a domain identifier uniquely associatedwith and identifying the selected domain (e.g., a domain identifier for“acme.com”). In certain embodiments, when the selected domain is a newdomain (e.g., the user has selected the “Add domain” interface element),the domain access configuration request comprises a new domainidentifier to be associated with the new domain once permissioned.

In some embodiments, the application management system 200 (e.g.,product access configuration server 210) retrieves instance data and/ordomain data for populating a domain access configuration user interface.For example, in certain embodiments, the application management system200 (e.g., product access configuration server 210) queries one or morerepositories to populate the domain access configuration user interface500. In this regard, in some embodiments, using the organizationidentifier associated with the admin user, the application managementsystem 200 (e.g., product access configuration server 210) queries anapplications repository for instance data corresponding to the pluralityof application instances associated with the organization. For instance,in some embodiments, the instance data associated with an applicationinstance comprises one or more of an application instance identifier, anapplication instance name, an application instance URL, domainpermissions profile(s), a set of available product roles for eachapplication instance, application instance plan identifier, or acombination thereof In certain embodiments, the application managementsystem 200 (e.g., the product access configuration server 210) retrievesdomain data (e.g., domain name(s), enablement/disablement status for thedomain(s), date each domain was added, date each domain was last edited,etc.) associated with the selected domain. In some embodiments, theapplication management system 200 (e.g., the product accessconfiguration server 210) retrieves one or more additional data items tobe included or rendered as part of the domain access configuration userinterface 500, including but not limited to, application name for eachapplication instance associated with the domain and application logo foreach application instance associated with the domain. In still furtherembodiments, using the organization identifier and/or a domainidentifier associated with the selected domain, the applicationmanagement system 200 (e.g., product access configuration server 210)queries a permissions repository for domain permissions profilesassociated with the organization and/or domain identifier. For example,in certain embodiments wherein the selected domain is a domain that hasbeen previously-permissioned with respect to at least one applicationinstance associated with the organization, the application managementsystem 200 (e.g., product access configuration server 210) populates theproduct role selection interface elements of the correspondingapplication instances in the domain access configuration user interfacebased on the product roles previously assigned to or associated with theapplication instances in accordance with the domain permissionsprofile(s) returned by the query, as described herein. In still furtherembodiments, retrieved domain permissions profile(s) are used topopulate the corresponding admin approval parameter data values.

As illustrated, the domain access configuration user interfaces 500 ofFIGS. 5A and 5D are configured to enable a user (e.g., an admin user) toconfigure and/or centrally manage domain-based access permissions of aplurality of application instances with respect to a selected domain.Specifically, the domain access configuration user interface 500presents instance data associated with one or more applicationinstances, for example, an application instance access set 508. In someembodiments, the application instance access set 508 (e.g., the depictedone or more application instances) is associated with the organizationof the admin user. In this regard, in some embodiments, the domainaccess configuration user interface 500 presents a plurality ofapplication instance components (e.g., an application instance accessset 508), each application instance component representing a respectiveapplication instance of a plurality of application instances associatedwith the organization.

It should be appreciated that the domain access configuration userinterfaces 500 may be configured to include various parameters or dataassociated with the domain or a particular application instance, andsuch parameters or data are not limited to the exemplary parameters anddata depicted in FIGS. 5A-5F. In some embodiments, a domain accessconfiguration user interface 500 comprises a domain name interfacecomponent 510. A domain name interface component 510 is a user interfaceelement that is rendered as a portion of a domain access configurationuser interface 500 and is configured to enable a user (e.g., admin user)to create and/or modify a domain name (e.g., text string or data value)for the selected domain. In some embodiments, the domain name interfacecomponent 510 includes a data value for a parameter representing anidentification of the selected domain. In some embodiments, the domainname interface component 510 of the domain access configuration userinterface, for example, an add new domain access configuration userinterface 500 as illustrated in FIG. 5A, comprises an example of thetext string to be entered to create a domain (e.g., yourcompany.com in agreyed typeset). In some embodiments, the selected domain is the domainof the organization (e.g., associated with the organization identifier).In some embodiments, the selected domain is domain not associated or isexternal to the organization (e.g., not associated with the organizationidentifier). In certain embodiments, user entry of a text stringidentifying the domain to be created is required. In still furtherembodiments, for example, in association with an add new domain accessconfiguration user interface 500, in response to user entry of a textstring in the domain name interface component 510, the product accessconfiguration server 210 determines whether the text string correspondsto a domain that already exists with respect to the organization (e.g.,a previously-permissioned domain). In certain embodiments, the productaccess configuration server 210 queries one or more repositories (e.g.,permissions repository 215 and/or applications repository 220) based onthe text string. In an instance in which the text string corresponds toa domain that already exists (e.g., a previously-permissioned domainreturned by the query(ies), such as acme.com), in some embodiments, theproduct access configuration server 210 is configured to cause renderingof a notification to the domain access configuration user interface 500indicating that the domain already exists. In still further embodiments,the product access configuration server 210 is configured to causerendering of a link, the selection of which by the admin userfacilitates access to an edit domain access configuration user interface(e.g., edit domain access configuration user interface 500 in FIG. 5D)associated with the previously-permissioned domain, the edit domainaccess configuration user interface 500 populated with permissions dataassociated with identified domain. For example, the product accessconfiguration server 210 populates each product role selection interfaceelement with a product role corresponding to the respective applicationinstance based on the one or more domain permissions profiles stored inassociation with the identified domain, as described herein.

Additionally or alternatively, in some embodiments, the domain nameinterface component 510 is associated with a domain name template, thedomain name template comprising a nomenclature and/or formattingstructure defining the required layout of the domain name text string.For example, in some embodiments, the entry of a comma (“,”) as part ofthe text string in the domain name interface component 510 (e.g.,“acme,com”) is not allowed according to a domain name templateassociated with interface component 510. In certain embodiments, theproduct access configuration server 210 is configured to cause renderingof a notification to the domain access configuration user interface 500indicating that the text string entered is invalid as a domain name.

As illustrated in FIGS. 5A and 5D, in some embodiments, a product namecolumn 502 includes a data value for a parameter representing anidentification of each application instance represented in theapplication instance access set 508. For example, “Confluence HR” and“Confluence External” are presented in the first and second row,respectively, of the application instance access set 508 in theexemplary domain access configuration user interfaces 500 depicted inFIGS. 5A and 5D. In some further embodiments, additional identifyinginformation is displayed in the product name column 502 to uniquelyidentify the corresponding application instance. For example, asillustrated in FIGS. 5A and 5D, the “Confluence HR” application instancecomponent presented in the first row of the application instance accessset 508 also includes a data value for a parameter representing a URL orsite with which the application instance is associated (e.g.,“acme-hr.atlassian.net”). For example, a user may attempt to access suchapplication instance of Confluence® at acme-hr.atlassian.net/confluence.The exemplary “Confluence External” application instance componentpresented in the second row of the application instance access set 508also includes a data value for a parameter representing a URL or sitewith which the application instance is associated (e.g.,“acme-CS.atlassian.net”). For example, a user may attempt to access suchapplication instance of Confluence® at acme-CS.atlassian.net/confluence.Accordingly, at least two separate application instances of Confluence®are associated with Acme Corporation at different URLs or sites. Itshould be appreciated that the product name column 502 may be configuredto include any of various types of information to more particularlyidentify or distinguish the corresponding application instance from theother application instances. For example, in at least some exampleembodiments, the product name column 502 is configured to include one ormore additional application instance identifier(s).

Additionally or alternatively, as illustrated, a product role column 504includes a data value for a parameter representing the product role tobe associated with users of the selected domain in association with thecorresponding application instance. For example, in some embodiments, adomain access configuration user interface 500 comprises a product roleselection interface element 520 rendered in association with eachapplication instance component, each product role selection interfaceelement 520 configured to receive a product role selection, therebyenabling a user (e.g., admin user) to define (e.g., select) a productrole to be assigned to the selected domain with respect to accessing thecorresponding application instance. In some embodiments, each productrole selection interface element 520 is populated with one or moreavailable product role(s) associated with the selected applicationinstance. For example, in some embodiments, instance data stored in apermissions repository and/or an applications repository comprises aplurality of available product role(s) for each application instance. Aproduct role is associated with (e.g., defines) a level or type ofaccess to a product or resource (e.g., application instance). Forexample, in the example embodiment illustrated in FIG. 5A, product roleshave not yet been associated or assigned to any of the correspondingapplication instances depicted in the domain access configuration userinterface 500 (e.g., add new domain access configuration userinterface). In certain such embodiments, the product role selectioninterface is defaulted to “None”, indicating that users associated withthe selected domain currently do not have access to the correspondingapplication instance (e.g., without additional admin approval).

Turning to the example embodiment illustrated in FIG. 5D, product roleshave been previously assigned or associated with each of the depictedapplication instances. For example, in the non-limiting exampleillustrated in FIG. 5D, when attempting to access the Confluence®application instance at acme-hr.atlassian.net, users associated with orcredentialed with the “acme.com” domain (e.g., users attempting toaccess an application instance having an email domain of @acme.com intheir email address) are permissioned to access such applicationinstance in accordance with a “User” role. In a further non-limitingexample, when attempting to access the Confluence® External applicationinstance at acme-CS.atlassian.net, users associated with or credentialedwith the “acme.com” domain are permissioned to access such applicationinstance in accordance with a “Helpseeker” product role. In someembodiments, the level or type of access associated with a selectedproduct role is a default associated with the application managementsystem 200 or the particular application instance. In some furtherembodiments, the level or type of access associated with a selectedproduct role, and even the existence or creation of a product role, isseparately configurable by the organization (e.g., via an admin user).For example, in some embodiments, a plurality of product roles can beassociated with an organization, the level or type of access associatedwith each product role being separately definable and made available toany one or more a plurality of application instances associated with theorganization. In certain embodiments, revisions and changes made to thelevel or type of access associated with a product role applies to allapplication instances in which the product role is an available productrole, allowing quick and efficient changes to access permissions.

Additionally or alternatively, in some embodiments, user interactionwith a product role selection interface element 520 generates a productrole selection request associated with the corresponding applicationinstance with respect to the selected domain. For example, in thenon-limiting example illustrated in FIG. 5B, an admin user has selectedthe drop-down menu associated with the product role selection interfaceelement 520, revealing available product roles associated with thecorresponding application instance of Confluence® HR atacme-hr.atlassian.net (e.g., an available product roles set includingNone, Guest, User, and Auditor roles). In some embodiments, asillustrated in FIG. 5B, each available product role is rendered with abrief summary or description of the type of access associated withproduct role. The admin user interacts or engages with the depictedavailable product roles set to select a product role to be associatedwith the corresponding application instance for the selected domain of“xyz.com”, thereby generating a product role selection request. Forexample, in response to user interaction with the product role selectioninterface element 520 to select the “Auditor” product role, a productrole selection request is generated at a client device (e.g., an admindevice 103A-103N) and transmitted to the application management system200 (e.g., product access configuration server 210). In someembodiments, the product role selection request comprises a product roleidentifier associated with the selected product role. In the embodimentsdepicted in FIGS. 5A-5C, the product role selection interface element520 is depicted as a drop-down menu. Such example of a product roleselection interface element 520, however, is for purposes ofillustration and not of limitation and other suitable variations ofdepicting a product role selection interface element are alsocontemplated by this disclosure as will be apparent to one of ordinaryskill in the art. For example, in some embodiments, a checkbox interfaceelement or radio button is associated with each available product role.

In the non-limiting example illustrated in FIG. 5E, although a “User”product role was previously populated in the product role selectioninterface element 520, an admin user has now selected the drop-down menuassociated with the product role selection interface element 520,revealing available product roles associated with the correspondingapplication instance of Confluence® HR at acme-hr.atlassian.net (e.g.,an available product roles set including “None”, “Guest”, “User”, and“Auditor” product roles) for the acme.com domain. In some embodiments,as illustrated in FIG. 5E, each available product role is rendered witha brief summary or description of the type of access associated withproduct role. The admin user interacts or engages with the depictedavailable product roles set to select a new, updated product role to beassociated with the corresponding application instance for the selecteddomain of “acme.com”, thereby generating a product role selectionrequest. For example, in response to user interaction with the productrole selection interface element 520 to select the “Guest” product role,a product role selection request is generated at a client device (e.g.,an admin device 103A-103N) and transmitted to the application managementsystem 200 (e.g., product access configuration server 210). In someembodiments, the product role selection request comprises a product roleidentifier associated with the selected product role. In the embodimentsdepicted in FIGS. 5D-5F, the product role selection interface element520 is depicted as a drop-down menu. Such example of a product roleselection interface element 520, however, is for purposes ofillustration and not of limitation and other suitable variations ofdepicting a product role selection interface element are alsocontemplated by this disclosure as will be apparent to one of ordinaryskill in the art. For example, in some embodiments, a checkbox interfaceelement or radio button is associated with each available product role.

In some embodiments, an application management system 200 (e.g., productaccess configuration server 210) causes rendering of an updated domainaccess configuration user interface 500. In some embodiments, suchrendering of an updated domain access configuration user interface 500is performed in response to receiving the product role selection requestfrom the admin device 103A-103N. In the non-limiting example of theembodiments illustrated in FIGS. 5B and 5C, the admin user has selectedthe “Auditor” product role for the “xyz.com” domain with respect to theConfluence® HR application instance at acme-hr.atlassian.net, and theapplication management system 200 (e.g., product access configurationserver 210) causes rendering of the updated domain access configurationuser interface 500 as depicted in FIG. 5C. Similarly, in thenon-limiting example of the embodiments illustrated in FIGS. 5E and 5F,the admin user has selected the “Guest” product role for the “acme.com”domain with respect to the Confluence® HR application instance atacme-hr.atlassian.net, and the application management system 200 (e.g.,product access configuration server 210) causes rendering of the updateddomain access configuration user interface 500 as depicted in FIG. 5F.

Returning to the data value(s) depicted in a domain access configurationuser interface 500, additionally or alternatively, in some embodiments,an admin approval column 506 includes a data value for a parameterrepresenting whether or not admin approval is to be required for usersassociated with the selected domain to access the correspondingapplication instance. For example, in some embodiments, as illustratedin FIG. 5D, a domain access configuration user interface 500 comprisesan admin approval user interface element 530 rendered in associationwith each application instance component, each admin approval userinterface element 530 configured to receive an indication of an adminapproval parameter request, thereby enabling a user (e.g., admin user)to define an admin approval access parameter associated with thecorresponding application instance. As depicted in the exampleillustrated in FIG. 5D, in some embodiments, the admin approval userinterface element 530 is a checkbox interface element, the selection ofwhich indicates that admin approval is to be required for usersassociated with the selected domain to access the correspondingapplication instance. In such embodiments, when such admin approval isenabled with respect to a particular application instance, even a userfrom an approved (e.g., managed) domain associated with an assignedproduct role defining at least some level of access (e.g., “User”,“Helpseeker”, or the like, as opposed to “None”) still requires approvalfrom an admin user before being granted access to the particularapplication instance. For example, in the non-limiting exampleillustrated in FIG. 5D, further admin approval is still required for auser associated with the acme.com domain when accessing the Confluence®Internal application instance to be granted access according to the“User” product role. In a further non-limiting example illustrated inFIG. 5D, further admin approval is not required for a user associatedwith the acme.com domain when accessing the Confluence® Externalapplication instance at acme-CS.atlassian.net. In such example, anacme.com user would be granted access in accordance with the“Helpseeker” role to such application instance without requirement offurther admin approval.

In some embodiments, admin approval required is a default data value orsetting for the admin approval column 506. In some other embodiments, noadmin approval required is a default data value or setting for the adminapproval column 506. The admin user interacts or engages with thedepicted admin approval user interface element 530 (e.g., checking thecheckbox interface element or unchecking the checkbox interfaceelement), thereby generating an admin approval parameter request inaccordance with the admin approval parameter. In some embodiments, theadmin approval parameter request is generated at a client device (e.g.,an admin device 103A-103N) and transmitted to the application managementsystem 200 (e.g., product access configuration server 210). In someembodiments, the admin approval parameter request comprises an adminapproval identifier and/or admin approval access parameter associatedwith the selection. The admin approval user interface element 530 allowsan admin user to quickly and easily enable or disable the requirementfor admin approval at the domain level for each application instance.

In some embodiments, the application management system 200 (e.g.,product access configuration server 210) receives a product roleselection request in response to user interaction with a product roleselection interface element 520. Similarly, in some embodiments, theapplication management system 200 (e.g., product access configurationserver 210) receives an approval admin parameter request in response touser interaction with an admin approval user interface element 530. Forexample, in some embodiments, product role selection request(s) and/orapproval admin parameter request(s) are generated by the admin device103A-103N and transmitted to the product access configuration server 210each time the admin user adds, removes, selects, and/or otherwiseinteracts with the respective product role selection interface 520 oradmin approval user interface element 530 to permission a selecteddomain with respect to a plurality of application instances, such thatthe admin user experiences passively saved changes or modifications.

Additionally or alternatively, in some embodiments, product roleselection request(s) and/or approval admin parameter request(s)generated by the admin device 103A-103N each time the user adds,removes, selects, and/or otherwise interacts with the respective productrole selection interface 520 or approval user interface element 530,however, the product role selection request(s) and/or approval adminparameter request(s) are only transmitted to the product accessconfiguration server 210 upon a further affirmative selection by theadmin user. For example, in some embodiments, a client session isinitiated by or on the admin device 103A-103N in association with thedomain access configuration request in order to capture anymodifications or changes (e.g., additions, deletions, selections, etc.)detected in association with a domain access configuration userinterface 500 and causes an “Add” (e.g., in association with an add newdomain access configuration user interface) or “Save” (e.g., inassociation with an edit domain access configuration user interface)icon, actuator button, or other executable interface element 512 to berendered to the domain access configuration user interface 500 inresponse to such detections. In association with detecting aninteraction with the “Add” or “Save” icon, actuator button, or otherexecutable interface element 512 associated with authorizing additions,changes, or modifications, the admin device 103A-103N transmits allcaptured product role selection request(s) and/or approval adminparameter request(s) associated with the detected additions, changes, ormodifications. In still further embodiments, if no interaction with the“Add” or “Save” icon, actuator button, or other executable interfaceelement 512 is detected, or interaction with a “Cancel” icon, actuatorbutton, or other executable interface element 514 is detected, the admindevice does not transmit such captured product role selection request(s)and/or approval admin parameter request(s) to the apparatus (e.g.,product access configuration server 210).

Additionally or alternatively, in some embodiments, as illustrated inFIG. 5D, a domain access configuration user interface comprises a“Remove” or “Delete” icon, button, or interface element 540. In someembodiments, user interaction with a “Remove” or “Delete” icon, button,or interface element 540 generates a remove domain request at the admindevice 103A-103N and transmits such request to the product accessconfiguration server 210. The product access configuration server 210 isconfigured to generate and cause a confirmation interface (not depicted)comprising a remove domain confirmation component (e.g., “Confirm”actuator button) to be rendered to or in association with the domainaccess configuration user interface 500. In some embodiments, theconfirmation interface comprises a notification regarding usersassociated with selected domain no longer being able to access theorganization's products or resources (e.g., without an individualinvitation). In response to confirmation of such removal request, theproduct access configuration server 210 causes deletion of thepermissioned domain from corresponding repository.

Additionally or alternatively, in some embodiments, as illustrated inFIGS. 5A-5F, the domain access configuration user interface 500comprises an admin notification configuration interface element 550. Insome embodiments, user interaction with an admin notificationconfiguration interface element 550 generates an admin notificationrequest at the admin device 103A-103N and transmits such request to theproduct access configuration server 210. The admin notification requestis received by the product access configuration server 210. The adminnotification request comprises an admin notification parameter, theadmin notification parameter defining if and when admin users associatedwith the organization are to receive notification of users of theselected domain obtain access to a resource. For example, in someembodiments, user interaction with a radio button of the adminnotification configuration interface element 550 indicates admin usersare to be sent a notification upon each instance a user gains access toa resource. In some embodiments, user interaction with a radio button ofthe admin notification configuration interface element 550 indicatesadmin users are to be sent a notification when a user requires adminapproval to gain access to a resource. In further embodiments, userinteraction with a radio button of the admin notification configurationinterface element 550 indicates no notifications relative to users ofthe selected domain gaining access are to be sent to admin users. Inother embodiments, no such notifications sent if none of the radiobuttons are selected by the user. In still further embodiments, userinteraction with a radio button of the admin notification configurationinterface element 550 indicates selection of one or more admin users toreceive notifications. As depicted in FIG. 5A, in some embodiments, userinteraction with a search field, dropdown menu, and/or picker fielddefines the admin notification parameters.

In some embodiments, user interaction with the domain accessconfiguration user interface 500 enables variable domain provisioning inthe application management system 200 (e.g., product accessconfiguration server 210). For example, in some embodiments, in responseto receiving a product role selection request, the applicationmanagement system 200 (e.g., product access configuration server 210)generates a domain permissions profile associated with the selecteddomain, the domain permissions profile being a data structure comprisinga plurality of application instances, each application instanceassociated with a corresponding product role (e.g., based on the productrole selection request). The product role defines the role-based domainaccess permission of the selected domain (e.g., users associated withthe selected domain) for accessing the selected application instanceassociated with the product role selection request. With respect togenerating a domain permissions profile, the term “generates” refers toboth creating a domain permissions profile in a first instance (e.g., inassociation with an add domain access configuration user interface) andalso to updating a domain permissions profile in a subsequent instance(e.g., in association with an edit domain access configuration userinterface).

Additionally or alternatively, in certain embodiments, in response toreceiving a product role selection request, the application managementsystem 200 (e.g., product access configuration server 210) generates anapplication instance permissions profile associated with thecorresponding application instance, the application instance permissionsprofile being a data structure comprising one or more permissioneddomains, each domain associated with a corresponding product role (e.g.,based on the product role selection request). The product role definesthe role-based domain access permission of the corresponding domain(e.g., users associated with the domain) for accessing the selectedapplication instance. With respect to generating an application instancepermissions profile, the term “generates” refers to both creating anapplication instance permissions profile in a first instance (e.g., inassociation with permissioning a domain with respect to the applicationinstance for the first time) and also to updating an existingapplication instance permissions profile in a subsequent instance (e.g.,in association with revising and/or editing a product role associatedwith a domain that has previously been permissioned, permissioning asecond domain after a first domain has previously been permissioned withrespect to the application instance, etc.). In some embodiments, such anapplication instance permissions profile can be subsequently queried bythe application management system 200 (e.g., product accessconfiguration server 210) to determine if a user's email domain isidentified as an approved (e.g., permissioned) domain associated with arequested application instance based on an application instanceidentifier associated with the requested application instance.

FIG. 6A illustrates an example product access user interface 600structured in accordance with various embodiments of the presentdisclosure. In some embodiments, the product access user interface 600is rendered to a client device, for example, a user device 101A-101Nassociated with a user. For instance, in some embodiments, utilizing anapplication instance URL for access to a desired application instance, auser is redirected to and presented with the product access userinterface 600 depicted in FIG. 6A. For example, in some embodiments, auser associated with xyz.com who attempts to access the applicationinstance of Confluence® HR at acme-hr.atlassian.net/confluence isredirected to and presented with the product access user interface 600depicted in FIG. 6A. In such an instance wherein the parsed email domainmatches a previously-permissioned (e.g., approved) domain of xyz.com, asdiscussed with respect to FIGS. 5A-5C, the user has access to theapplication instance in accordance with the “Auditor” role-based domainaccess permission, and in some embodiments, simply selects the “Join on{orgName}” interface element to obtain access to the requestedapplication instance.

FIG. 6B illustrates an example request product access user interface650. When the domain associated with a user is approved/permissioned toaccess the requested application instance, however, an admin approvalaccess parameter associated with the selected resource of that domainindicates approval by an admin user is required before a user is grantedaccess to the selected resource (e.g., an application instance),

in some embodiments, the product access configuration server 210 causesrendering of a request product access user interface, such as depictedby request product access user interface 650 in FIG. 6B, to a visualdisplay of the user device 101A associated with the access applicationinstance request.

Although not depicted, in an example instance wherein the domainassociated with a user requesting access to a selected applicationinstance is either not permissioned to access the requested applicationinstance (e.g., domain is not recognized with respect to thecorresponding application instance), the domain enablement data valuehas been disabled, or the product role associated with the domain forthe requested application instance is determined to be, for example,“None” or “No product access”, the product access configuration server210 directs the user to, and causes rendering of, an error userinterface (e.g., “You do not have access to this product. If this isincorrect, please contact your Atlassian admin.”) to a visual display ofthe user device 101A associated with the access application instancerequest.

EXAMPLE OPERATIONS FOR MANAGING ACCESS PERMISSIONS FOR A PLURALITY OFAPPLICATION INSTANCES

Turning now to FIG. 7A, a flowchart broadly illustrates a series ofoperations or process blocks for managing access permissions for aplurality of application instances, in accordance with some exampleembodiments of the present disclosure. The example operations of FIG. 7Aare illustrated from the perspective of an application management system200. The operations illustrated in FIG. 7A may, for example, beperformed by, with the assistance of, and/or under the control of one ormore apparatuses, such as product access configuration server 210, asdescribed above. In this regard, performance of the operations mayinvoke one or more of memory 201, processor 202, input/output circuitry203, communications circuitry 204, and/or permissions circuitry 205.

In the embodiment illustrated in FIG. 7A, as shown in operation 705, theapparatus (e.g., product access configuration server 210) includesmeans, such as input/output circuitry 203, communications circuitry 204,and/or the like, for receiving a manage access permissions request. Insome embodiments, this request is received from a computing deviceassociated with an admin user, such as admin device 103A-103N. In somefurther embodiments, this request is received via a network 102, asillustrated in FIG. 1 . However, in some embodiments, this informationis received by direct user input using input/output circuitry 203. Instill further embodiments, the manage access permissions requestcomprises a unique identifier, such as an organization identifierassociated with the admin user and/or an admin user identifier fromwhich the organization identifier can be determined and/or extracted. Byway of a non-limiting exemplary illustration, Jennifer is an admin userfor Acme Corporation and in response to Jennifer selecting the “UserAccess Settings” interface element associated with an administrationuser interface for Acme Corporation in the application management system200, a manage access permissions request, comprising an organizationidentifier associated with Acme Corporation, is generated at Jennifer'sadmin device and transmitted via a network to the apparatus (e.g.,product access configuration server 210).

In operation 710, the apparatus (e.g., product access configurationserver 210) includes means, such as processor 202, input/outputcircuitry 203, communications circuitry 204, permissions circuitry 205and/or the like, for causing rendering of a centralized access userinterface to a visual display of the computing device associated withthe admin user (e.g., an admin device 103A-103N) in response toreceiving the manage access permissions request. As described herein,the centralized access user interface is configured for managing accesspermissions of one or more domains. For example, in a non-limitingexemplary illustration, in response to receiving the manage accesspermissions request from the admin device associated with Jennifer, theapparatus (e.g., product access configuration server 210) causesrendering of a centralized access user interface to the visual displayof Jennifer's admin device. In one embodiment, the centralized accessuser interface comprises a listing of one or more manageable domains asdescribed above with respect to FIG. 4 .

In operation 715, the apparatus (e.g., product access configurationserver 210) includes means, such as processor 202, input/outputcircuitry 203, communications circuitry 204, permissions circuitry 205and/or the like, for receiving a domain access configuration requestassociated with a first domain in response to user interaction with thecentralized access user interface. For example, in a non-limitingexemplary illustration, in response to Jennifer's selection of the “Adddomain” interface element in the exemplary centralized access userinterface depicted in FIG. 4 , a domain access configuration requestassociated with a new domain to be permissioned is generated byJennifer's admin device and transmitted to and received by the productaccess configuration server 210. In certain embodiments, the domainaccess configuration request optionally further comprises a createdomain request requesting creation of the new domain for configurationof the access permissions of the new domain. In a similar non-limitingexemplary illustration, in response to Jennifer's selection of the“Edit” interface element associated with the “acme.com” domain listed inthe exemplary centralized access user interface depicted in FIG. 4 , adomain access configuration request associated with thepreviously-permissioned “acme.com” domain is generated by Jennifer'sadmin device and transmitted to and received by the product accessconfiguration server 210. In certain embodiments, the domain accessconfiguration request optionally further comprises a modify domainrequest requesting modification of the access permissions of thepreviously-permissioned domain (e.g., “acme.com” domain).

In operation 720, the apparatus (e.g., product access configurationserver 210) includes means, such as processor 202, input/outputcircuitry 203, communications circuitry 204, permissions circuitry 205and/or the like, for retrieving instance data associated with aplurality of application instances, each application instance associatedwith the organization identifier. In some embodiments, the apparatus(e.g., product access configuration server 210) retrieves such instancedata from one or more repositories, such as a permissions repositoryand/or an applications repository. In some embodiments, instance dataassociated with an application instance comprises one or more of anapplication instance identifier, an application instance name, anapplication instance URL, a domain permissions profile, a set ofavailable product roles. By way of a non-limiting exemplaryillustration, the product access configuration server 210 retrievesinstance data for a plurality of application instances based on AcmeCorporation's organization identifier. In some embodiments, such as inthe context of the non-limiting example of Jennifer editing the accesspermissions for “acme.com”, retrieving instance data by the productaccess configuration server 210 optionally comprises querying apermissions repository for domain permissions profiles associated withthe previously-permissioned domain (e.g., acme.com).

In operation 725, the apparatus (e.g., product access configurationserver 210) includes means, such as processor 202, input/outputcircuitry 203, communications circuitry 204, permissions circuitry 205and/or the like, for causing rendering of a domain access configurationuser interface associated with the first domain. In some embodiments,the retrieved instance data is used to populate the domain accessconfiguration user interface such that the domain access configurationuser interface is based on at least the instance data. The domain accessconfiguration user interface comprises a plurality of applicationinstance components, wherein each application instance componentrepresents a respective application instance of the plurality ofapplication instances. In some embodiments, the domain accessconfiguration user interface further comprises a product role selectioninterface element in association with each application instancecomponent. By way of a non-limiting exemplary illustration, the productaccess configuration server 210 causes rendering of an add new domainaccess configuration user interface (e.g., domain access configurationuser interface 500 depicted in FIG. 5A) in response to receiving thedomain access configuration request associated with a new domain inoperation 715. In another non-limiting exemplary illustration, theproduct access configuration server 210 causes rendering of an editdomain access configuration user interface (e.g., domain accessconfiguration user interface 500 depicted in FIG. 5D) in response toreceiving the domain access configuration request associated with thepreviously-permissioned “acme.com” domain in operation 715.

Thereafter, in operation 730, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, permissionscircuitry 205 and/or the like, for receiving a first product roleselection request in response to user interaction with a product roleselection interface element corresponding to a first applicationinstance. By way of a non-limiting exemplary illustration, Jenniferinteracts with the product role selection interface elementcorresponding to “Confluence HR” application instance at“acme-HR.atlassian.net” to select the “Auditor” product role (e.g.,domain access configuration user interface 500 depicted in FIGS. 5B and5C) for the new “xyz.com” domain, thereby generating a product roleselection request at Jennifer's admin device and transmitting theproduct role selection request to be received by the product accessconfiguration server 210. In another non-limiting exemplaryillustration, Jennifer interacts with the product role selectioninterface element corresponding to “Confluence HR” application instanceat “acme-hr.atlassian.net” to select the “Guest” product role (e.g.,domain access configuration user interface 500 depicted in FIGS. 5E and5F) for the “acme.com” domain, thereby generating a product roleselection request at Jennifer's admin device and transmitting theproduct role selection request to be received by the product accessconfiguration server 210.

Subsequently, in operation 735, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,permissions circuitry 205 and/or the like, for generating a first domainpermissions profile. In some embodiments, the first domain permissionsprofile comprises at least a first product role associated with thefirst application instance, the first product role defining therole-based domain access permission of the first domain for accessingthe first application instance.

By way of a non-limiting exemplary illustration, in response toJennifer's selection of the “Auditor” product role with respect to the“Confluence HR” application instance at “acme-hr.atlassian.net” in theadd new domain access configuration user interface associated with“xyz.com” as described above with respect to operation 730 (e.g.,receipt by the product access configuration server 210 of the productrole selection request from Jennifer's admin device), the product accessconfiguration server 210 generates a domain permissions profile withrespect to “xyz.com”. In such non-limiting example, the xyz.com domainpermissions profile comprises at least the “Auditor” product role isassociation with the “Confluence HR” application instance at“acme-hr.atlassian.net” (e.g., in association with an applicationinstance identifier for such application instance). For context, the“Auditor” product role defines the role-based domain access permissionof “xyz.com” for accessing the “Confluence HR” application instance at“acme-hr.atlassian.net”.

By way of another non-limiting exemplary illustration, in response toJennifer's selection of the “Guest” product role with respect to the“Confluence HR” application instance at “acme-hr.atlassian.net” in theedit domain access configuration user interface associated with“acme.com” as described above with respect to operation 730 (e.g.,receipt by the product access configuration server 210 of the productrole selection request from Jennifer's admin device), the product accessconfiguration server 210 generates (e.g., updates) the domainpermissions profile associated with acme.com. In this example, the term“generates” refers to updating the domain permissions profile, as theacme.com domain permissions profile already exists. In such non-limitingexample, the acme.com domain permissions profile comprises at least the“Guest” product role (instead of the “User” product role) in associationwith the “Confluence HR” application instance at “acme-hr.atlassian.net”(e.g., in association with an application instance identifier for suchapplication instance). For context, the “Guest” product role defines therole-based domain access permission of “acme.com” for accessing the“Confluence HR” application instance at “acme-hr.atlassian.net”.

Additionally or alternatively, in certain embodiments, the apparatus(e.g., product access configuration server 210) includes means, such asprocessor 202, permissions circuitry 205 and/or the like, for generatinga first application instance permissions profile associated with thefirst application instance, wherein the first application instancepermissions profile comprises at least the first domain, the firstdomain associated with a corresponding product role defining therole-based domain access permission of the first domain for accessingthe first application instance.

Subsequently, in operation 740, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,permissions circuitry 205 and/or the like, for storing the first domainpermissions profile in a permissions repository in association with thefirst domain and the first application instance. Additionally oralternatively, in certain embodiments, the apparatus (e.g., productaccess configuration server 210) includes means, such as processor 202,permissions circuitry 205 and/or the like, for storing the firstapplication instance permissions profile in a permissions repository inassociation with the first application instance and the first domain. Insome embodiments, such an application instance permissions profile canbe subsequently queried by the application management system 200 (e.g.,product access configuration server 210) to determine if a user's emaildomain is identified as an approved (e.g., permissioned) domainassociated with a requested application instance based on an applicationinstance identifier associated with the requested application instance.

FIG. 7B is a signal diagram of an example data flow represented by theoperations depicted in FIG. 7A. That is, FIG. 7B illustrates an examplesignal diagram illustrating data flow interactions between a productaccess configuration server, a repository, and an admin device whenmanaging access permissions for a plurality of application instances inaccordance with one embodiment. FIG. 7B is described as being performedby a product access configuration server 210, an permissions repository215, and an admin device 103A. These may be similar to those previouslydiscussed with regards to FIG. 1 .

Turning now to FIG. 8 , a flowchart broadly illustrates another seriesof operations or process blocks for managing access permissions for aplurality of application instances such that a single domain can beassociated with variable product roles in relation to multipleapplication instances, in accordance with some example embodiments ofthe present disclosure. The example operations of FIG. 8 are illustratedfrom the perspective of an application management system. The operationsillustrated in FIG. 8 may, for example, be performed by, with theassistance of, and/or under the control of one or more apparatuses, suchas product access configuration server 210, as described above. In thisregard, performance of the operations may invoke one or more of memory201, processor 202, input/output circuitry 203, communications circuitry204, and/or permissions circuitry 205.

In the embodiment illustrated in FIG. 8 , as shown in operation 805, theapparatus (e.g., product access configuration server 210) includesmeans, such as input/output circuitry 203, communications circuitry 204,and/or the like, for receiving a second product role selection requestin response to user interaction with a product role selection interfaceelement associated with a second application instance. Continuing thenon-limiting exemplary illustration of admin user Jennifer permissioning“xyz.com” to have an “Auditor” product role with respect to a firstinstance of Confluence® (e.g., the Confluence HR application instance atacme-hr.atlassian.net), Jennifer further interacts with the product roleselection interface element corresponding to a second applicationinstance of Confluence® (e.g., “Confluence External” applicationinstance at “acme.atlassian.net” as illustrated in the domain accessconfiguration user interface 500 depicted in FIGS. 5B and 5C) to selecta “Customer” product role for the “xyz.com” domain, thereby generating aproduct role selection request at Jennifer's admin device andtransmitting the product role selection request to be received by theproduct access configuration server 210.

Subsequently, in operation 810, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,permissions circuitry 205 and/or the like, for updating the first domainpermissions profile. In some embodiments, the updated first domainpermissions profile comprises at least the first product role associatedwith the first application instance and a second product role associatedwith the second application instance, the first product role and secondproduct role defining the role-based domain access permissions of thefirst domain for accessing the first application instance and secondapplication instance, respectively. For example, the xyz.com domainpermissions profile comprises the “Auditor” product role in associationwith the first application instance (e.g., the Confluence HR applicationinstance at acme-hr.atlassian.net) and the “Customer” product role inassociation with the second application instance (e.g., the “ConfluenceExternal” application instance at “acme. atlassian.net”).

Subsequently, in operation 815, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,permissions circuitry 205 and/or the like, for storing the updated firstdomain permissions profile in a permissions repository in associationwith the first domain, the first application instance, and the secondapplication instance. For instance, continuing with the non-limitingxyz.com domain example, the xyz.com domain permissions profile is storedin association with xyz.com, the Confluence® HR application instance,and the Confluence® External application instance for Acme Corporation,thereby allowing Jennifer to centrally manage access permissions of aplurality of application instances while enabling variable domainpermissioning across such plurality of application instances based onrole-based domain access permissions.

Turning now to FIG. 9 , a flowchart broadly illustrates another seriesof operations or process blocks for managing access permissions for aplurality of application instances such that variable domains can beassociated with different product roles in relation to a singleapplication instance, in accordance with some example embodiments of thepresent disclosure. The example operations of FIG. 9 are illustratedfrom the perspective of an application management system 200. Theoperations illustrated in FIG. 9 may, for example, be performed by, withthe assistance of, and/or under the control of one or more apparatuses,such as product access configuration server 210, as described above. Inthis regard, performance of the operations may invoke one or more ofmemory 201, processor 202, input/output circuitry 203, communicationscircuitry 204, and/or permissions circuitry 205.

In the embodiment illustrated in FIG. 9 as shown in operation 905, theapparatus (e.g., product access configuration server 210) includesmeans, such as input/output circuitry 203, communications circuitry 204,and/or the like, for receiving a domain access configuration requestassociated with a second domain in response to user interaction with thecentralized access user interface. Continuing the non-limiting exemplaryillustration of admin user Jennifer permissioning “xyz.com” to have an“Auditor” product role with respect to a first instance of Confluence®(e.g., the Confluence HR application instance at acme-hr.atlassian.net),Jennifer further interacts with the “Edit” interface element associatedwith a second domain “acme.com” in the centralized access userinterface, thereby generating a domain access configuration requestassociated with “acme.com” at Jennifer's admin device and transmittingthe domain access configuration request to be received by the productaccess configuration server 210.

Subsequently, in operation 910, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, permissionscircuitry 205 and/or the like, for causing rendering, based on thepreviously-retrieved instance data, of a domain access configurationuser interface associated with the second domain (e.g., acme.com asillustrated in FIG. 5D).

Thereafter, in operation 915, the apparatus (e.g., product accessconfiguration server 210) includes means, such as input/output circuitry203, communications circuitry 204, and/or the like, for receiving asecond product role selection request in response to user interactionwith a product role selection interface element associated with thefirst application instance. Continuing the non-limiting exemplaryillustration, admin user Jennifer further interacts with the productrole selection interface element corresponding to the first applicationinstance of Confluence® (e.g., “Confluence HR” application instance at“acme-hr.atlassian.net” as illustrated in the domain accessconfiguration user interface 500 depicted in FIGS. 5E and 5F) to selectan “Guest” product role for the “acme.com” domain, thereby generating aproduct role selection request at Jennifer's admin device andtransmitting the product role selection request to be received by theproduct access configuration server 210.

Subsequently, in operation 920, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,permissions circuitry 205 and/or the like, for generating a seconddomain permissions profile, wherein the second domain permissionsprofile comprises a second product role associated with the firstapplication instance, the second product role defining the role-baseddomain access permission of the second domain for accessing the firstapplication instance. In a non-limiting example, the product accessconfiguration server 210 generates (e.g., updates) an acme.com domainpermissions profile to reflect the “Guest” product role for acme.comwith respect to the first application instance (e.g., “Confluence HR”application instance at “acme-hr.atlassian.net”) such that the acme.comdomain permissions profile comprises the “Guest” product role associatedwith the Confluence® HR application instance, the “Guest” product roledefining the role-based domain access permission of acme.com users foraccessing the first application instance (e.g., “Confluence HR”application instance at “acme-hr.atlassian.net”).

In operation 925, the apparatus (e.g., product access configurationserver 210) includes means, such as processor 202, permissions circuitry205 and/or the like, for storing the second domain permissions profilein the permissions repository in association with the second domain andthe first application instance. Continuing the non-limiting exemplaryillustration, the product access configuration server 210 stores theacme.com domain permissions profile in association with the acme.comdomain and the Confluence® HR application instance (e.g., atacme-hr.atlassian.net). In some embodiments, unique identifiersassociated with each object (e.g., application instance identifier,domain identifier(s), etc.) are stored in association. Accordingly, insome embodiments, the permissions repository comprises a plurality ofdomain permissions profiles. By way of non-limiting example, thepermissions repository comprises a xyz.com domain permissions profile,wherein the xyz.com domain is associated with an “Auditor” product rolewith respect to the Confluence® HR application instance and furthercomprises an acme.com domain permissions profile, wherein the acme.comdomain is associated with an “Guest” product role with respect to theConfluence® HR application instance, thereby allowing Jennifer tocentrally manage access permissions of a plurality of applicationinstances while enabling variable permissioning across at least oneapplication instance based on role-based domain access permissions.

Turning now to FIG. 10A, a flowchart broadly illustrates another seriesof operations or process blocks for programmatically managing accesspermissions for a plurality of application instances to provide a userwith access to an application instance in accordance with a role-baseddomain access permission, in accordance with some example embodiments ofthe present disclosure. The example operations of FIG. 10A areillustrated from the perspective of an application management system.The operations illustrated in FIG. 10A may, for example, be performedby, with the assistance of, and/or under the control of one or moreapparatuses, such as product access configuration server 210, asdescribed above. In this regard, performance of the operations mayinvoke one or more of memory 201, processor 202, input/output circuitry203, communications circuitry 204, and/or permissions circuitry 205.

In the embodiment illustrated in FIG. 10A, as shown in operation 1005,the apparatus (e.g., product access configuration server 210) includesmeans, such as input/output circuitry 203, communications circuitry 204,and/or the like, for receiving an access application instance requestassociated with an application instance. In some embodiments, therequested application instance is associated with an organization andthe access application instance request comprises a user email addressidentifier associated with a user. In some embodiments, this request isreceived from a computing device associated with the user, such as userdevice 101A-101N. In some further embodiments, this request is receivedvia a network 102, as illustrated in FIG. 1 . In still furtherembodiments, the access application instance request comprises one ormore unique identifiers, such as an organization identifier with whichthe requested application instance is associated, an applicationinstance identifier associated with the requested application instance,a user email address identifier associated with the user, and/or acombination thereof. For example, in some embodiments, a user simplyprovides login credentials, including an email address, through theinterface of their user device 101A-101N. For example, if the user isnot logged into their Atlassian account and the user attempts to accessthe application instance URL for a selected instance of Confluence®, theapplication management system (e.g., product access configuration server210) detects and/or determines that the user has not logged in based onthe user's session/cookie history. In some such embodiments, the productaccess configuration server 210 causes redirection of the user to a URLto provide the user's login credentials (e.g., login.atlassian.com). Incertain embodiments, after receiving and authenticating the user's logincredentials, the product access configuration server 210 redirects theauthenticated user back to the selected application instance URL. Theuser device 101A-101N then transfers the unique user email addressidentifier to the application management system 200 (e.g., the productaccess configuration server 210) as part of or in addition to the accessapplication instance request. In some embodiments, the user attempts toaccess the requested application instance via the URL associated withthe application instance (e.g., acme.atlassian.net/Confluence), theattempt thereby generating the access application instance request atthe user device 101A-101N to be transmitted to the product accessconfiguration server 210. By way of a non-limiting exemplaryillustration, Bob is a user employed by XYZ Corporation with an emailaddress of bob@xyz.com. In such example, Bob attempts to access theConfluence® HR application instance at acme.atlassian.net. Bob isre-directed to a landing page wherein he provides his user emailaddress. In some embodiments, the provided user email address identifierand an identifier associated with the requested application instance aretransmitted with the access application instance request.

Subsequently, in operation 1010, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,input/output circuitry 203, permissions circuitry 205 and/or the like,for parsing the user email address identifier for an email domain. Forexample, Bob's email address of bob@xyz.com is parsed to identify thexyz.com domain.

Thereafter, in operation 1015, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,input/output circuitry 203, permissions circuitry 205 and/or the like,for querying a permissions repository (e.g., permissions repository 215)for a domain permissions profile based on the parsed email domain. Inthe non-limiting exemplary example, the product access configurationserver 210 queries the permissions repository 215 based on the parsedxyz.com email domain. Additionally or alternatively, in certainembodiments, the apparatus (e.g., product access configuration server210) includes means, such as processor 202, input/output circuitry 203,permissions circuitry 205 and/or the like, for querying a permissionsrepository (e.g., permissions repository 215) for an applicationinstance permissions profile based on the application instanceidentifier associated with the requested application instance.

Subsequently, in operation 1020, in an instance wherein a domainpermissions profile is returned based on the query, the apparatus (e.g.,product access configuration server 210) includes means, such asprocessor 202, input/output circuitry 203, permissions circuitry 205and/or the like, for determining whether the returned domain permissionsprofile comprises a product role associated with the requestedapplication instance. With respect to the above-described non-limitingexample, the product access configuration server 210 determines whetherthe returned xyz.com domain permissions profile comprises a product roleassociated with the requested Confluence® HR application instance.Additionally or alternatively, in certain embodiments, the apparatus(e.g., product access configuration server 210) includes means, such asprocessor 202, input/output circuitry 203, permissions circuitry 205and/or the like, for determining whether the returned applicationinstance permissions profile comprises the parsed email domain. In suchinstance wherein the parsed email domain is included in the applicationinstance permissions profile, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,input/output circuitry 203, permissions circuitry 205 and/or the like,for further determining whether a product role is associated with theparsed email domain in the application instance permissions profile.With respect to the above-described non-limiting example, the productaccess configuration server 210 determines whether a returnedConfluence® HR application instance permissions profile comprisesxyz.com domain, and if so, whether a product role is associated with thexyz.com domain.

In operation 1025, in an instance wherein the domain permissions profilecomprises a product role associated with the requested applicationinstance, the apparatus (e.g., product access configuration server 210)includes means, such as processor 202, input/output circuitry 203,permissions circuitry 205 and/or the like, for providing the user withaccess to the requested application instance based on a role-baseddomain access permission corresponding to the identified product role.For example, the product access configuration server 210 provides Bobwith access to the Confluence® HR application instance (e.g., directsBob's web browser to the URL of the application instance) with “Auditor”role-based domain access permission. In the event that the identifiedproduct role defines no product access (e.g., product role is identifiedas “None”), the user is required to request access from theorganization. The request product access process is described in greaterdetail below with respect to FIG. 11 .

FIG. 10B is a signal diagram of an example data flow represented by theoperations depicted in FIG. 10A. That is, FIG. 10B illustrates anexample signal diagram illustrating data flow interactions between aproduct access configuration server, a repository, and a user devicewhen programmatically managing access permissions for a plurality ofapplication instances in accordance with one embodiment. FIG. 10B isdescribed as being performed by a product access configuration server210, a permissions repository 215, and a user device 101A. These may besimilar to those previously discussed with regards to FIG. 1 .

Turning now to FIG. 11 , a flowchart broadly illustrates another seriesof operations or process blocks for programmatically managing accesspermissions for a plurality of application instances in response to anaccess application instance request associated with an unauthorizeddomain, in accordance with some example embodiments of the presentdisclosure. The example operations of FIG. 11 are illustrated from theperspective of an application management system. The operationsillustrated in FIG. 11 may, for example, be performed by, with theassistance of, and/or under the control of one or more apparatuses, suchas product access configuration server 210, as described above. In thisregard, performance of the operations may invoke one or more of memory201, processor 202, input/output circuitry 203, communications circuitry204, and/or permissions circuitry 205.

In the embodiment illustrated in FIG. 11 , as shown in operation 1105,the apparatus (e.g., product access configuration server 210) includesmeans, such as processor 202, input/output circuitry 203, communicationscircuitry 204, permissions circuitry 205 and/or the like, for causingrendering of a request product access user interface to a visual displayof a computing device associated with the access application instancerequest. For example, in some embodiments, the product accessconfiguration server 210 causes rendering of a request product accessuser interface, such as the request product access user interface 650 asdepicted in FIG. 6B to a visual display of the user device 101Aassociated with the access application instance request.

Thereafter, as shown in operation 1110, the apparatus (e.g., productaccess configuration server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, permissionscircuitry 205 and/or the like, for receiving a request product accessrequest associated with the requested application instance in responseto user interaction with the request product access user interface.

Subsequently, in operation 1115, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, permissionscircuitry 205 and/or the like, for generating a request product accessnotification associated with the requested application instance, therequest product access notification comprising the user email addressidentifier.

Thereafter, in operation 1120, the apparatus (e.g., product accessconfiguration server 210) includes means, such as processor 202,input/output circuitry 203, communications circuitry 204, permissionscircuitry 205 and/or the like, for transmitting the request productaccess notification to at least one admin user associated with theorganization. For example, in some embodiments, the request productaccess notification is an email or is associated with an email sent toone or more admin users associated with the organization. In stillfurther embodiments, the request product access notification isassociated with an access requests user interface 1200 as depicted inFIG. 12 , wherein an admin user can review a plurality of requestproduct access requests and associated data. In some embodiments, theaccess requests user interface 1200 comprises an access user column1202, which includes a data value for a parameter representing a userfor whom access is being requested (e.g., user identifier, user emailaddress identifier, etc.). In some embodiments, the access requests userinterface 1200 comprises an access requestor column 1204, which includesa data value for a parameter representing the requesting user and infurther embodiments, a data value representing lapse of time sincerequest was made. In still further embodiments, the access requests userinterface 1200 comprises an associated product(s) column 1206, whichincludes a data value for a parameter representing one or more products(e.g., applications, application instances, references) associated withthe request product access notification. In further embodiments, theaccess requests user interface 1200 comprises an available action(s)column 1208, which includes a data value for a parameter representingone or more potentially available further action(s) for handling therequest product access notification (e.g., approve now, deny, requestmore information concerning the request, etc.).

FIGS. 7A, 7B, 8, 9, 10A, 10B, and 11 thus illustrate flowcharts andsignal diagrams describing the operation of apparatuses, methods,systems, and computer program products according to example embodimentscontemplated herein. It will be understood that each flowchart block,and combinations of flowchart blocks, may be implemented by variousmeans, such as hardware, firmware, processor, circuitry, and/or otherdevices associated with execution of software including one or morecomputer program instructions. For example, one or more of theoperations described above may be implemented by an apparatus executingcomputer program instructions. In this regard, the computer programinstructions may be stored by a memory 201 of the product accessconfiguration server 210 and executed by a processor 202 of the productaccess configuration server 210. As will be appreciated, any suchcomputer program instructions may be loaded onto a computer or otherprogrammable apparatus (e.g., hardware) to produce a machine, such thatthe resulting computer or other programmable apparatus implementsvarious functions, including those functions specified in the flowchartblocks. These computer program instructions may also be stored in acomputer-readable memory that may direct a computer or otherprogrammable apparatus to function in a particular manner, such that theinstructions stored in the computer-readable memory produce an articleof manufacture, the execution of which implements the functionsspecified in the flowchart blocks. The computer program instructions mayalso be loaded onto a computer or other programmable apparatus to causea series of operations to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions executed on the computer or other programmableapparatus provide operations for implementing the functions specified inthe flowchart blocks.

The flowchart blocks support combinations of means for performing thespecified functions and combinations of operations for performing thespecified functions. It will be understood that one or more blocks ofthe flowcharts, and combinations of blocks in the flowcharts, can beimplemented by special purpose hardware-based computer systems whichperform the specified functions, or combinations of special purposehardware with computer instructions.

Thus, particular embodiments of the subject matter have been described.While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as description offeatures specific to particular embodiments of particular inventions.Other embodiments are within the scope of the following claims. Certainfeatures that are described herein in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub-combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults, unless described otherwise. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system components in the embodiments describedabove should not be understood as requiring such separation in allembodiments, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products. Anyoperational step shown in broken lines in one or more flow diagramsillustrated herein are optional for purposes of the depicted embodiment.

In some cases, the actions recited in the claims can be performed in adifferent order and still achieve desirable results. In addition, theprocesses depicted in the accompanying figures do not necessarilyrequire the particular order shown, or sequential order, to achievedesirable results, unless described otherwise. In certainimplementations, multitasking and parallel processing may beadvantageous.

CONCLUSION

Many modifications and other embodiments of the present disclosure setforth herein will come to mind to one skilled in the art to which thisdisclosure pertains having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the disclosure is not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Moreover, although the foregoing descriptions and the associateddrawings describe example embodiments in the context of certain examplecombinations of elements and/or functions, it should be appreciated thatdifferent combinations of elements and/or functions may be provided byalternative embodiments without departing from the scope of the appendedclaims. In this regard, for example, different combinations of elementsand/or functions than those explicitly described above are alsocontemplated as may be set forth in some of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

1. An apparatus for managing access permissions for a plurality ofapplication instances associated with an organization, the apparatuscomprising at least one processor and at least one non-transitory memoryincluding program code, the at least one non-transitory memory and theprogram code configured to, with the at least one processor, cause theapparatus to: receive a manage access permissions request from acomputing device associated with an admin user, the manage accesspermissions request comprising an organization identifier; causerendering of a centralized access user interface to a visual display ofthe computing device associated with the admin user in response toreceiving the manage access permissions request, the centralized accessuser interface configured for managing access permissions of one or moredomains; receive a domain access configuration request associated with afirst domain in response to user interaction with the centralized accessuser interface; retrieve instance data associated with a plurality ofapplication instances, each application instance associated with theorganization identifier; cause rendering, based on at least the instancedata, of a domain access configuration user interface associated withthe first domain, the domain access configuration user interfacecomprising a plurality of application instance components, wherein eachapplication instance component represents a respective applicationinstance of the plurality of application instances and comprises aproduct role selection interface element; receive a first product roleselection request in response to user interaction with a product roleselection interface element corresponding to a first applicationinstance; generate a first domain permissions profile, wherein the firstdomain permissions profile comprises at least a first product roleassociated with the first application instance, the first product roledefining the role-based domain access permission of the first domain foraccessing the first application instance; and store the first domainpermissions profile in a permissions repository in association with thefirst domain and the first application instance.
 2. The apparatus ofclaim 1, wherein the first domain is a domain that has not beenpreviously permissioned such that the domain access configurationrequest comprises a create domain request requesting creation of thefirst domain and configuration of the access permissions of the firstdomain.
 3. The apparatus of claim 1, wherein the first domain is apreviously-permissioned domain such that domain access configurationrequest comprises a modify domain request requesting modification of theaccess permissions of the first domain.
 4. The apparatus of claim 3,wherein retrieving instance data associated with the plurality ofapplication instances comprises: querying the permissions repository fordomain permissions profiles associated with the first domain.
 5. Theapparatus of claim 4, wherein causing rendering of the domain accessconfiguration user interface associated with the first domain comprises:populating each product role selection interface element with a productrole corresponding to the respective application instance based on thedomain permissions profiles returned by the query.
 6. The apparatus ofclaim 1, wherein the at least one non-transitory memory and the programcode further are configured to, with the at least one processor, causethe apparatus to: receive a second product role selection request inresponse to user interaction with a product role selection interfaceelement associated with a second application instance; update the firstdomain permissions profile such that the first domain permissionsprofile comprises at least the first product role associated with thefirst application instance and a second product role associated with thesecond application instance, the first product role and second productrole defining the role-based domain access permissions of the firstdomain for accessing the first application instance and secondapplication instance, respectively; and store the updated first domainpermissions profile in the permissions repository in association withthe first domain, the first application instance, and the secondapplication instance.
 7. The apparatus of claim 1, wherein the at leastone non-transitory memory and the program code further are configuredto, with the at least one processor, cause the apparatus to: receive adomain access configuration request associated with a second domain inresponse to user interaction with the centralized access user interface;cause rendering, based on the instance data, of a domain accessconfiguration user interface associated with the second domain; receivea second product role selection request in response to user interactionwith a product role selection interface element associated with thefirst application instance; generate a second domain permissionsprofile, wherein the second domain permissions profile comprises asecond product role associated with the first application instance, thesecond product role defining the role-based domain access permission ofthe second domain for accessing the first application instance; andstore the second domain permissions profile in the permissionsrepository in association with the second domain and the firstapplication instance.
 8. (canceled)
 9. (canceled)
 10. The apparatus ofclaim 1, wherein the domain access configuration user interface furthercomprises an admin approval user interface element associated with eachapplication instance component of the plurality of application instancecomponents, the admin approval user interface element configured forreceiving an admin approval parameter request.
 11. The apparatus ofclaim 1, wherein the instance data associated with an applicationinstance comprises one or more of an application instance identifier, anapplication instance name, an application instance URL, an applicationinstance permissions profile, a set of available product roles.
 12. Theapparatus of claim 1, wherein the product role selection interfaceelement for the first application instance is associated with aplurality of available product roles.
 13. The apparatus of claim 12,wherein the product role selection interface element for the firstapplication instance comprises a drop down menu, the drop down menulisting the plurality of available product roles associated with thefirst application instance, the product role selection interface elementconfigured to receive a product role selection.
 14. (canceled) 15.(canceled)
 16. A method for managing access permissions for a pluralityof application instances associated with an organization, the methodcomprising: receiving a manage access permissions request from acomputing device associated with an admin user, the manage accesspermissions request comprising an organization identifier; causingrendering of a centralized access user interface to a visual display ofthe computing device associated with the admin user in response toreceiving the manage access permissions request, the centralized accessuser interface configured for managing access permissions of one or moredomains; receiving a domain access configuration request associated witha first domain in response to user interaction with the centralizedaccess user interface; retrieving instance data associated with aplurality of application instances, each application instance associatedwith the organization identifier; causing rendering, based on at leastthe instance data, of a domain access configuration user interfaceassociated with the first domain, the domain access configuration userinterface comprising a plurality of application instance components,wherein each application instance component represents a respectiveapplication instance of the plurality of application instances andcomprises a product role selection interface element; receiving a firstproduct role selection request in response to user interaction with aproduct role selection interface element corresponding to a firstapplication instance; generating a first domain permissions profile,wherein the first domain permissions profile comprises at least a firstproduct role associated with the first application instance, the firstproduct role defining the role-based domain access permission of thefirst domain for accessing the first application instance; and storingthe first domain permissions profile in a permissions repository inassociation with the first domain and the first application instance.17. The method of claim 16, wherein the first domain is a domain thathas not been previously permissioned such that the domain accessconfiguration request comprises a create domain request requestingcreation of the first domain and configuration of the access permissionsof the first domain.
 18. The method of claim 16, wherein the firstdomain is a previously-permissioned domain such that domain accessconfiguration request comprises a modify domain request requestingmodification of the access permissions of the first domain.
 19. Themethod of claim 18, wherein retrieving instance data associated with theplurality of application instances comprises: querying the permissionsrepository for domain permissions profiles associated with the firstdomain.
 20. The method of claim 19, wherein causing rendering of thedomain access configuration user interface associated with the firstdomain comprises: populating each product role selection interfaceelement with a product role corresponding to the respective applicationinstance based on the domain permissions profiles returned by the query.21. The method of claim 16, the method further comprising: receiving asecond product role selection request in response to user interactionwith a product role selection interface element associated with a secondapplication instance; updating the first domain permissions profile suchthat the first permissions profile comprises at least the first productrole associated with the first application instance and a second productrole associated with the second application instance, the first productrole and second product role defining the role-based domain accesspermissions of the first domain for accessing the first applicationinstance and second application instance, respectively; and storing theupdated first domain permissions profile in the permissions repositoryin association with the first domain, the first application instance,and the second application instance.
 22. The method of claim 16, themethod further comprising: receiving a domain access configurationrequest associated with a second domain in response to user interactionwith the centralized access user interface; causing rendering, based onthe instance data, of a domain access configuration user interfaceassociated with the second domain; receiving a second product roleselection request in response to user interaction with a product roleselection interface element associated with the first applicationinstance; generating a second domain permissions profile, wherein thesecond domain permissions profile comprises a second product roleassociated with the first application instance, the second product roledefining the role-based domain access permission of the second domainfor accessing the first application instance; and storing the seconddomain permissions profile in the permissions repository in associationwith the second domain and the first application instance.
 22. Themethod of claim 16, the method further comprising: receiving a domainaccess configuration request associated with a second domain in responseto user interaction with the centralized access user interface; causingrendering, based on the instance data, of a domain access configurationuser interface associated with the second domain; receiving a secondproduct role selection request in response to user interaction with aproduct role selection interface element associated with the firstapplication instance; generating a second domain permissions profile,wherein the second domain permissions profile comprises a second productrole associated with the first application instance, the second productrole defining the role-based domain access permission of the seconddomain for accessing the first application instance; and storing thesecond domain permissions profile in the permissions repository inassociation with the second domain and the first application instance.23. (canceled)
 24. (canceled)
 25. The method of claim 16, wherein thedomain access configuration user interface further comprises an adminapproval user interface element associated with each applicationinstance component of the plurality of application instance components,the admin approval user interface element configured for receiving anadmin approval parameter request.
 26. The method of claim 16, whereinthe instance data associated with an application instance comprises oneor more of an application instance identifier, an application instancename, an application instance URL, a domain permissions profile, and aset of available product roles.
 27. The method of claim 16, wherein theproduct role selection interface element for the first applicationinstance is associated with a plurality of available product roles. 28.The method of claim 27, wherein the product role selection interfaceelement for the first application instance comprises a drop down menu,the drop down menu listing the plurality of available product rolesassociated with the first application instance, the product roleselection interface element configured to receive a product roleselection.
 29. (canceled)
 30. (canceled)